Closed jsmrcina closed 3 years ago
A bit more testing shows that this is actually due to the output directory not being present when the program launches. The directory is then created for the log file so if you re-run the binary, it will create the syncHistory.json file automatically.
I think the fix here is just to pre-create the output directory if it doesn't exist when reading the configuration.
Thanks for the two bugs! I can definitely fix both of these, however, I have family in town for the next week so my free time to address these may be limited. But know they are on my radar!
No problem -- happy to help and there's no rush here. When you get a chance to look, please let me know if you have any trouble repro'ing and I can provide additional details as necessary. Have a great week with your family!
Fix for this has been pushed. Please open a new ticket if you continue to observe the issue.
Downloading the distribution ZIP from latest V2 branch, unzipping and configuring using the configuration JSON and then running the console app will crash with a file not found exception when looking for the syncHistory.json file as it does not exist.
To workaround, you must create the DB file by hand and put an empty JSON object into it:
Note that path may need to be adjusted if the configuration file property SyncHistoryDbPath was changed. Once this file exists, the sync runs as expected.
Also note that this only seems to happen on first run. If I delete the syncHistory.json file after a sync is finished, it will re-create the file correctly.
One final detail is that the directory does exist (even though the exception claims it is a directory missing error) -- only the file is missing:
Exception text is below: