search

flaxsearch / flaxcode

Automatically exported from code.google.com/p/flaxcode
4 stars 1 forks source link

Indexing stops; here you are the log - timestamp out of range for platform localtime #193

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello 
During indexation, the Flax basic stops and in the log I can see

2008-08-11 17:48:28,065: filtering.remote_filter: 1288: WARNING: Killing 
remote filter - it raised the exception: (-
2147286960, 'STG_E_FILEALREADYEXISTS', None, None):
2008-08-11 17:48:28,065: indexing.remote: 1288: ERROR: Filtering file: 
C:\U\Doc\gerly.doc with filter: 
<indexserver.remote_filter.RemoteFilterRunner object at 0x00CB87F0> 
exception com_error((-2147286960, 'STG_E_FILEALREADYEXISTS', None, None)), 
skipping:
2008-08-11 17:48:30,467: indexing.remote: 1288: ERROR: Unhandled error in 
do_indexing, traceback is: Traceback (most recent call last):
  File "indexserver\indexer.pyo", line 144, in do_indexing
  File "filespec.pyo", line 78, in files
  File "filespec.pyo", line 118, in included
ValueError: timestamp out of range for platform localtime()/gmtime() 
function
:
2008-08-11 17:48:30,467: indexing.remote: 1288: CRITICAL: Unhandled 
exception in IndexerProcess.run(), traceback follows:
 Traceback (most recent call last):
  File "indexserver\indexer.pyo", line 288, in run
  File "indexserver\indexer.pyo", line 144, in do_indexing
  File "filespec.pyo", line 78, in files
  File "filespec.pyo", line 118, in included
ValueError: timestamp out of range for platform localtime()/gmtime() 
function

What is this?
How to solve this issue?
Regards

Original issue reported on code.google.com by robi...@gmail.com on 11 Aug 2008 at 4:01

GoogleCodeExporter commented 9 years ago 
Looking at the code, it seems like datetime.fromtimestamp() is throwing an 
exception
because the result of os.path.getmtime() is outside the range it can cope with. 
It
seems from a quick search that os.path.getmtime() on Windows can return 
unreliable
file modification times in some cases. We should check the returned values 
before
passing them to fromtimestamp().

As a temporary workaround, is it possible to open the file in question and 
re-save it
with a new timestamp?

Original comment by charliej...@gmail.com on 15 Aug 2008 at 9:08

GoogleCodeExporter commented 9 years ago 
Hello Charlie and thank you very much for your comment.
The files that generate this problem are from the 20th century (1996 - 1997).
Can be this?
Now i try to open them and save it again, so the timestamp will change in 2008.
I'll let you know.
Regards
Roberto

Original comment by robi...@gmail.com on 15 Aug 2008 at 10:08

GoogleCodeExporter commented 9 years ago 
It shouldn't be the fact that the files are from before the millenium; it's more
likely that their timestamp is corrupted somehow.

Original comment by charliej...@gmail.com on 15 Aug 2008 at 12:56

GoogleCodeExporter commented 9 years ago 
Hello Charlie; I opened them, saved them and still get that error; very strange.

Original comment by robi...@gmail.com on 16 Aug 2008 at 7:34

GoogleCodeExporter commented 9 years ago

Original comment by charliej...@gmail.com on 27 Aug 2009 at 1:24