jakesylvestre / pychess

Automatically exported from code.google.com/p/pychess
GNU General Public License v3.0
1 stars 7 forks source link

'NoneType' object is not callable, issue happens in /System/glock.py #635

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Unsure

What is the expected output? What do you see instead?
No error; instead I see:

Original exception was:
Traceback (most recent call last):
  File "/home/avius/Progging/Mercurial/aviwlevy-gtkspinbutton/lib/pychess/System/glock.py", line 45, in handler
    acquire()
  File "/home/avius/Progging/Mercurial/aviwlevy-gtkspinbutton/lib/pychess/System/glock.py", line 13, in acquire
    me = currentThread()
  File "/usr/lib/python2.6/threading.py", line 810, in currentThread
    return _active[_get_ident()]
TypeError: 'NoneType' object is not callable

This is repeatedly printed on the console.

Did you use PyChess from a repo, tarball, install or hg?
hg

Please attach the latest pychess logfile from ~/.local/share/pychess/
(I didn't attach because it is too large of an attachment, and relevant 
information is lost in the sea of debug messages one would expect during a long 
chess games session on FICS.)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by avi.w.l...@gmail.com on 8 Jan 2011 at 3:55

GoogleCodeExporter commented 9 years ago
Can you remember what you did in pychess when this happened?

Original comment by gbtami on 13 Jan 2011 at 5:45

GoogleCodeExporter commented 9 years ago
I'm sorry, it has been too long for me to remember. I tried to figure out what 
had happened right when the error happened and I recall not having much luck. 
It was during a session that involved a lot of FICS play and it seemed to have 
happened randomly.
I tried to upload the log, but google code would not allow me to do so due to 
it being such a large file. I then tried looking through the log manually to 
try to pull out relevant sections but this was also to no avail: most of the 
log was just debug spam about the goings-on at FICS (games created, seeks sent, 
rating changes, etc)
The best I have is to trace to glock.py but from this little information it is 
very difficult to figure out what happened. How would you describe the contents 
of glock.py?

Original comment by avi.w.l...@gmail.com on 14 Jan 2011 at 4:58

GoogleCodeExporter commented 9 years ago
The problem happens inside the system currentThread function, so there is not a 
lot we can do. Perhaps it should be reported to python upstream, but since we 
can't reproduce it, they wouldn't be able to help a lot.

Original comment by lobais on 15 Jan 2011 at 1:07

GoogleCodeExporter commented 9 years ago

Original comment by gbtami on 21 Apr 2013 at 7:14