search

rajrakeshdr / pychess

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

Error message on command line makes UI useless #157

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Sometimes I get this on the comment line when starting or loading a new
game, just at the beginnning.
Traceback (most recent call last):
  File "/home/tvermeir/svn/pychess/lib/pychess/Main.py", line 141, in
on_load_game1_activate
    ionest.loadGame ()
  File "/home/tvermeir/svn/pychess/lib/pychess/widgets/ionest.py", line
272, in loadGame
    game, gmwidg = runNewGameDialog(hideFC=False)
  File "/home/tvermeir/svn/pychess/lib/pychess/widgets/ionest.py", line
234, in runNewGameDialog
    engine0, args0 = engine1, args1 = anaengines[0]
IndexError: list index out of range

I don't have this all the time and I can't find a pattern how to reproduce
it. Maybe this output is usefull to someone...

Original issue reported on code.google.com by thijsver...@gmail.com on 4 Mar 2007 at 9:18

GoogleCodeExporter commented 9 years ago 
We always assume that we have at least one analyzing engine, as the PyChess 
engine
supports analyzing.

The problem is that the cecp code knows only if the engine can analyze, if it
responds to "protover 2" with "analyze=1".
This has a timeout on 2 seconds. So as the PyChess engine is rather slow to 
start up,
then if your computer is slow, or is doing something else, it might fail the 
timeout,
and we will have no analyzers (at least if you have no other engines installed).

I didn't think this was an issue anymore, as PyChess has begun to send analyse=1
before it imports anything, to make sure it is never late.

Which version do you use?

Original comment by lobais on 4 Mar 2007 at 10:50

GoogleCodeExporter commented 9 years ago 
I'm running the latest svn-code on a "slow" computer (1,2GHz). Maybe the 
timeout is a
little to short

Original comment by thijsver...@gmail.com on 4 Mar 2007 at 11:46

GoogleCodeExporter commented 9 years ago 
Hm, it's the same which xboard uses. Then ofcource xboard normally isn't 
supposed to
handle python engines ;)
If it is higher, engines which never respond, will cause the loading time of 
PyChess
to be highter too.
In 0.7 this is all fixed, using an xml based engine system, which caches 
information
on engines, and supports using no analyzers at all.

Perhaps you can try out different timeouts in the CECP.py file..

Original comment by lobais on 4 Mar 2007 at 12:23

GoogleCodeExporter commented 9 years ago 
Please reopen if this is reproducable in 0.8

Original comment by lobais on 28 Aug 2007 at 9:44