I/O operation on closed file

[GoogleCodeExporter]

ENGLISH ONLY.
ONLY BUGS, NOT FEATURE REQUEST (use the forum section for that)
IF ANY OF THE INFO BELOW IS MISSING THE BUG REPORT WILL BE DELETED.
Thank you.

Bot version: 2.2f Source
OGame server language: fr
OGame server version: v 0.76c
Using admirals or commander?: commander
Operating System: Windows XP

Description of the problem:

Log file contents:

Traceback (most recent call last):
  File "D:\XX\Python\lib\logging\handlers.py", line 73, in emit
    if self.shouldRollover(record):
  File "D:\XX\Python\lib\logging\handlers.py", line 147, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
07/17/07 XX:XX:XX ATTACKING XXXXXX [X:XXX:XX] from XXXXXX [X:XXX:X
 with {'largeCargo': 9}
Traceback (most recent call last):
  File "D:\XX\Python\lib\logging\handlers.py", line 73, in emit
    if self.shouldRollover(record):
  File "D:\XX\Python\lib\logging\handlers.py", line 147, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
07/17/07 XX:XX:XX ATTACKING XXXXXXXXX [X:XXX:XX] from XXXXX [X:XXX:X
 with {'largeCargo': 5}
Traceback (most recent call last):
  File "D:\XX\Python\lib\logging\handlers.py", line 73, in emit
    if self.shouldRollover(record):
  File "D:\XX\Python\lib\logging\handlers.py", line 147, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
07/17/07 XX:XX:XX XXXXXXXXX [X:XXX:XX] from XXXXX [X:XXX:X] with {'e
pionageProbe': 1}
Traceback (most recent call last):
  File "D:\XX\Python\lib\logging\handlers.py", line 73, in emit
    if self.shouldRollover(record):
  File "D:\XX\Python\lib\logging\handlers.py", line 147, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file

Please provide any additional information below:

Nothing special, the bot continue to attack, and it still crashes randomly
( you remember my previous posts said WontFix )
It's just a little portion of the complete log ...

Original issue reported on code.google.com by HenryZ...@gmail.com on 17 Jul 2007 at 12:06

[GoogleCodeExporter]

Original comment by jsceballos on 17 Jul 2007 at 6:09

• Changed state: Accepted
• Added labels: Language-ALL, Milestone-2.2d, OpSys-Linux, Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by kovansog...@gmail.com on 13 Jan 2009 at 3:26

• Changed state: OutOfDate