From metatracker at psf.upfronthosting.co.za  Sun Jul  8 11:15:16 2018
From: metatracker at psf.upfronthosting.co.za (John Rouillard)
Date: Sun, 08 Jul 2018 15:15:16 +0000
Subject: [Tracker-discuss] [issue644] 'Random Issue' Button isn't working
In-Reply-To: <1508803113.44.0.213398074469.issue644@psf.upfronthosting.co.za>
Message-ID: <1531062916.53.0.56676864532.issue644@psf.upfronthosting.co.za>


John Rouillard <rouilj+psf at cs.umb.edu> added the comment:

I found this same issue in other places in roundup.

Thanks to Joseph Myers (jsm) for explaining what I was seeing on the roundup-devel mailing list.

There is a fix for it now in roundup that will be released as version 1.6.

You don't have to make any changes to your Random Issue implementation,
but I thought it would be good to document that there was a fundamental
oversight that is fixed.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue644>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jul  8 11:29:10 2018
From: metatracker at psf.upfronthosting.co.za (Berker Peksag)
Date: Sun, 08 Jul 2018 15:29:10 +0000
Subject: [Tracker-discuss] [issue644] 'Random Issue' Button isn't working
In-Reply-To: <1508803113.44.0.213398074469.issue644@psf.upfronthosting.co.za>
Message-ID: <1531063750.75.0.56676864532.issue644@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the update, John.

For future readers, here's a link to the discussion on the roundup-devel list: https://sourceforge.net/p/roundup/mailman/roundup-devel/thread/20180708014103.75EE34C0A5C%40itserver6.localdomain/

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue644>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jul 17 05:05:54 2018
From: metatracker at psf.upfronthosting.co.za (zhaoya)
Date: Tue, 17 Jul 2018 09:05:54 +0000
Subject: [Tracker-discuss] [issue657] PyGILState_Release
 FatalError[auto-releasing thread-state, but no thread-state for this thread]
Message-ID: <1531818354.87.0.56676864532.issue657@psf.upfronthosting.co.za>


New submission from zhaoya <zhaoya881010 at 163.com>:

python2.7.15
i have three threads call pythonfuc,and always receive a error "auto-releasing thread-state,but no thread-state for this thread"
log:
2018-07-17T16:03:06+08:00 [INFO] py call function id:11113 1
8208: PyThread_acquire_lock(04AE3E20, 1) called
8208: PyThread_acquire_lock(04AE3E20, 1) -> 1
2018-07-17T16:03:06+08:00 [INFO] py call function id:11112 2
2018-07-17T16:03:06+08:00 [INFO] py call function id:11111 3
threadid:12944,auto-releasing thread-state,but no thread-state for this thread
threadid:11176,auto-releasing thread-state,but no thread-state for this thread
threadid:24708,auto-releasing thread-state,but no thread-state for this thread

code:
threads -->func CallFunction(lpfuncInfo *FuncInfo, arg1 interface{}, arg2, arg3 unsafe.Pointer){
pyGilState := python.PyGILState_Ensure()
......
python.PyGILState_Release(pyGilState)

}

i don't understand?be rather baffling other threads call PyGILState_Release  and threadstates is null.

----------
messages: 3522
nosy: zhaoya881010
priority: bug
status: unread
title: PyGILState_Release FatalError[auto-releasing thread-state,but no thread-state for this thread]

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue657>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jul 17 05:22:04 2018
From: metatracker at psf.upfronthosting.co.za (zhaoya)
Date: Tue, 17 Jul 2018 09:22:04 +0000
Subject: [Tracker-discuss] [issue657] PyGILState_Release
 FatalError[auto-releasing thread-state, but no thread-state for this thread]
In-Reply-To: <1531818354.87.0.56676864532.issue657@psf.upfronthosting.co.za>
Message-ID: <1531819324.27.0.56676864532.issue657@psf.upfronthosting.co.za>


zhaoya <zhaoya881010 at 163.com> added the comment:

logs:
2018-07-17T16:59:00+08:00 [INFO] py call function id:11113 1
16072: PyThread_acquire_lock(00FD9E90, 1) called
16072: PyThread_acquire_lock(00FD9E90, 1) -> 1
16072: PyThread_release_lock(00FD9E90) called
2018-07-17T16:59:00+08:00 [INFO] py call function id:11112 3
16072: PyThread_acquire_lock(04393E20, 1) called
2018-07-17T16:59:00+08:00 [INFO] py call function id:11111 2
23252: PyThread_acquire_lock(00FD9E90, 1) called
24372: PyThread_acquire_lock(04393E20, 1) called
23252: PyThread_acquire_lock(00FD9E90, 1) -> 1
16072: PyThread_acquire_lock(04393E20, 1) -> 1
23252: PyThread_release_lock(00FD9E90) called
23252: PyThread_acquire_lock(04393E20, 1) called
threadid:14128,auto-releasing thread-state,but no thread-state for this thread

threadid:16072,23252,24372 is my create.14128 othrer.

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue657>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jul 17 10:04:02 2018
From: metatracker at psf.upfronthosting.co.za (Berker Peksag)
Date: Tue, 17 Jul 2018 14:04:02 +0000
Subject: [Tracker-discuss] [issue657] PyGILState_Release
 FatalError[auto-releasing thread-state, but no thread-state for this thread]
In-Reply-To: <1531818354.87.0.56676864532.issue657@psf.upfronthosting.co.za>
Message-ID: <1531836242.12.0.56676864532.issue657@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the report, but this is not the correct place to report such issues. Please use https://bugs.python.org/ instead.

Also, I'd first try getting help on python-list (https://mail.python.org/mailman/listinfo/python-list) or stackoverflow.com as this looks like a problem in the application, not in Python.

----------
nosy: +berker.peksag
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue657>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jul 31 04:53:51 2018
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 31 Jul 2018 08:53:51 +0000
Subject: [Tracker-discuss] [issue656] Support GitHub Auth in Sidebar
In-Reply-To: <1529081123.16.0.947875510639.issue656@psf.upfronthosting.co.za>
Message-ID: <1533027231.0.0.56676864532.issue656@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Hi Eric,

How can I fix this issue? Repository URL, etc... 

Thanks

----------
nosy: +matrixise
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue656>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jul 31 10:04:21 2018
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Tue, 31 Jul 2018 14:04:21 +0000
Subject: [Tracker-discuss] [issue656] Support GitHub Auth in Sidebar
In-Reply-To: <1529081123.16.0.947875510639.issue656@psf.upfronthosting.co.za>
Message-ID: <1533045861.81.0.56676864532.issue656@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

in fact, there is this issue on Github https://github.com/python/bugs.python.org/issues/7

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue656>
_______________________________________________________