[Evernote] Fails to set some notes' dates

[przemhb]

I have just used 1.5.6 to import ENEX notes. Some of the 394 notes were not set dates according to the ones stored in the ENEX file. I end up with writing Python code to fix this. Interestingly os.utime() failed to set those dates also and I was forced to use win32file.SetFileTime().

[akosbalasko]

Hi @przemhb ,
Could you please give us a bit more details about the problematic notes? Do you see any aspect that distinguishes the failed ones from the notes converted correctly? The key point would be that what you recognized, the failure of os.utime().
Thanks a lot!

[przemhb]

Hi @akosbalasko

just tried to recreate the problem to give you some insight or attach some problematic notes, but... to my surprise another import of the same ENEX resulted in flawless import. But how can it be? The same ENEX, the same Obsidian and Importer. Could it be, that some bug in underlying Python library was fixed in between?

What I have changed for the test was the ENEX filename and selected to put output notes in a folder. The folder did not have " ' " in its name.

[akosbalasko]

@przemhb , it's strange definitely.
But what you mentioned in your first comment made me think: "Interestingly os.utime() failed too". It would mean that something has failed on a deeper level.
I checked the code and fs.utimesSync (os.utime equivalent in NodeJS) is not covered by try-catch, so if it fails, it will make the whole note-conversion fail, even if everything goes well until that point. I think handling possible exceptions in this function would be a good patch.
May I ask what you saw as a failure?

[przemhb]

@akosbalasko In the case of failed import a note's modification date and time was not set as in the ENEX file, but to current time (or creation time - not 100% sure after those few weeks). As an effect sorting by modification date was flawed with some old notes appearing on the top of the list.

[akosbalasko]

@przemhb , okok thanks! And when you run the import last time, you mentioned that it went well flawlessly. Do you mean that the import itself worked well and set the correct creation dates without the python script?

[przemhb]

@akosbalasko yes, import alone went just fine, so I wasn't forced to use my python script. Modification dates were as in source ENEX.