weird log file every time I open a database file (PGN)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start pychess, open pgn file
2. close pychess
3. two log files have been created, one has always the same size (tried
three times) of 4415371 and is full of "could not write data".

What is the expected output? What do you see instead?
I do not really know if this is a bug, but it looks suspicious.

Does it happen every time?
Yes, tried three times.

What version of the product are you using?
0.10 alpha

Did you use an installed version of PyChess or did you run in from a
tarball/svn?
getdeb.net deb package

Please provide any additional information below.
attaching pgn file (only pychess created and used it) and both log files
(both are from the same run of pychess)

Original issue reported on code.google.com by pe3...@gmail.com on 10 Jan 2009 at 10:57

Attachments:

• 2009-01-10_23-35-26.log
• 2009-01-10_23-36-22.log
• pychess_db.pgn

[GoogleCodeExporter]

I'm afraid I cannot reproduce.
Could it have something to do with the harddrive space? File location? File 
permissions?

As the following reformation shows, the error is highly recursive, and is 
likely to
have something to do with the log system:

23:38:47 Default Error:
    Could not write data
        'Traceback (most recent call last):'
    to pipe '<open file '<stderr>', mode 'w' at 0xb7e4b0b0>'

Could not write data
    '23:38:47 Default Error:
        Could not write data
            'Traceback (most recent call last):'
        to pipe '<open file '<stderr>', mode 'w' at 0xb7e4b0b0>''
to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>'

Could not write data
    'Could not write data
        '23:38:47 Default Error:
            Could not write data
                'Traceback (most recent call last):'
            to pipe '<open file '<stderr>', mode 'w' at 0xb7e4b0b0>''
    to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>''
to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>'

Could not write data
    'Could not write data
        'Could not write data
            '23:38:47 Default Error:
                Could not write data
                    'Traceback (most recent call last):'
                to pipe '<open file '<stderr>', mode 'w' at 0xb7e4b0b0>''
        to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>''
    to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>''
to pipe '<open file '<stdout>', mode 'w' at 0xb7e4b068>'

Original comment by lobais on 13 Jan 2009 at 2:59

[GoogleCodeExporter]

The first logfile is just fine, btw. Only the second one witnesses of a 
shut-down
problem.

Original comment by lobais on 13 Jan 2009 at 3:00

[GoogleCodeExporter]

Ok, I found that for each PyChess engine, new log is created (not for other 
engines),
but I am unable to consistently reproduce this. :-(
It happens once and then, but do not see any pattern.

Original comment by pe3...@gmail.com on 25 Jan 2009 at 5:21

[GoogleCodeExporter]

I'v seen this problem before too, but can't reproduce now.

Original comment by gbtami on 25 Jan 2009 at 9:52

[GoogleCodeExporter]

The 'PyChess Engine creates a log' problem, is because the log module is used 
when
playing PyChess with the FICS option. The CECP version doesn't use the log 
module for
anything, but if the engine writes to stderr, log will catch it.
If it is a problem (what I agree it might be) we can probably just put the 
'import
Log' call somewhere in the fics part.

Original comment by lobais on 25 Jan 2009 at 4:41

[GoogleCodeExporter]

I've commited a proposed fix. It targets the recursive part. If we can fix 
that, we
can look into the pgn problem.

Original comment by lobais on 1 Feb 2009 at 10:14

• Changed state: Accepted

[GoogleCodeExporter]

Please, can you see if this is entirely fixed in trunk, or if another problem 
appears?

Original comment by lobais on 9 Feb 2009 at 4:21

[GoogleCodeExporter]

I did installed svn and downloaded pychess-read-only using it - now it is 1401.
How do I run it? I am actually not quite sure that when I run pychess from 
downloaded
directory, it runs the newest version. At least I do not see any difference (do 
not
know where to look for it though). I have also installed from before 0.10alpha 
deb
package.
Is there a way to check version of running PyChess?

Original comment by pe3...@gmail.com on 23 Feb 2009 at 10:17

[GoogleCodeExporter]

If you downloaded it to your home into svn/pychess:

PYTHONPATH=~/svn/pychess/lib ~/svn/pychess/pychess

Maybe we have to add the svn rev to the about dialog, if it was run from source.

Original comment by gbtami on 23 Feb 2009 at 10:53

[GoogleCodeExporter]

Thanks for advice, gbtami. Now I found some updates so I suppose I am running 
the
newest version.

I am unable to reproduce (weird log) with "rev 1401". Maybe later we will see 
if this
still might a problem.

Original comment by pe3...@gmail.com on 23 Feb 2009 at 4:48

[GoogleCodeExporter]

Original comment by gbtami on 19 Mar 2009 at 8:11

• Added labels: Type-Defect

[GoogleCodeExporter]

Original comment by gbtami on 25 Jun 2009 at 9:17

• Changed state: Fixed