search

akosbalasko / yarle

Yarle - The ultimate converter of Evernote notes to Markdown
https://github.com/akosbalasko/yarle
MIT License
1.43k stars 84 forks source link

Desktop App Accumulates Jobs #257

Closed grantx2016 closed 3 years ago

grantx2016 commented 3 years ago

Steps to reproduce:

  1. Configure a migration job and run it ("Job A")
  2. Delete the output
  3. Configure another migration job and run it ("Job B") Expected output: Notes from Job B only Actual output: Notes from Jobs A and B (ie. It appears to run Job A again, before running Job B, even though only configured for Job B).

Weird! 🤔

Yarle Desktop Version: 4.0.6 macOS: 10.15.7

akosbalasko commented 3 years ago

Hi @grantx2016 ! jeah,I realized the same, thanks god it's not about accumulating the jobs, it simply does not clear the logs before the new configuration. The weird thing is that i afair unlink the log file.

akosbalasko commented 3 years ago

Hi @grantx2016 , It's fixed in version 4.0.9, the log file contains info about the current execution only.

grantx2016 commented 3 years ago

Great. Thanks @akosbalasko . 🕺

grantx2016 commented 3 years ago

Hi @grantx2016 , It's fixed in version 4.0.9, the log file contains info about the current execution only.

When using this version, aftering the clearing the log via the UI after the first run, and then re-running, no log is produced.

akosbalasko commented 3 years ago

Hi @grantx2016 , what do you mean on "clearing the log via UI after the first run"? Did you clear the textarea manually? Or did you close the app and then open it again? Or just left everything as they are, navigated back to step one without closing the app and then did the flow again?

grantx2016 commented 3 years ago

I cleared the log text in the UI manually, left the app open with the same settings, then re-ran with a different input .enex file. The app appears to run ok but no log is produced this time around.

FYI, I am doing this workflow as I am trying to troubleshoot conversion failures so I am using the same settings but inputting slightly different .enex files to try to locate the troublesome attachment that is causing the failure.

akosbalasko commented 3 years ago

ok, okay get it, thanks for the feedback. I tested it by closing-reopening the app, but this scenario does not fit your workfow as the settings are not stored if I'm right. Ok, let me check it out. Thank you!

akosbalasko commented 3 years ago

@grantx2016 Ok, I think the easiest way to make it work is to do not remove the logs manually, because it will be updated by the tool. If you don't erase the logs, it works. Tricky, btw :).

To prevent this manual modification of the logs I'll add a feat. to make that text area read only.

grantx2016 commented 3 years ago

OK. That will work for now. Thanks!