-
-
Notifications
You must be signed in to change notification settings - Fork 870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Crash after synchronizing with std.json.JSONException@std/json.d(315): JSONValue is not an object #2822
Comments
Thanks - I know where this is being generated from, however a fix will have to wait until tomorrow or Friday AEST. |
That's fine. Thanks! |
Unfortunately I am not going to be able to look at anything today - so looking at these issues will be another ~24 hrs or so - sorry. |
@dploeger
Augment the above with the instructions here on building your own Docker container: When you rebuild your Docker container, you should be running client version |
@abraunegg With these changes, our pipeline was successful today. I'll monitor the next days. |
Thanks for the confirmation |
* Add isValidUTCDateTime function to validate timestamp as received from OneDrive API to ensure it is valid * Use new function before attempting to call SysTime.fromISOExtString to ensure this call will be successful * If there is no timestamp in the JSON, set it to the system time * Add assertion when building an item from DB data * Add new function (isValidUTF8) to check UTF-8 validity of a string before timestamp regex check * In a --resync scenario, if the file hash is the same, use the online timestamp as source of truth * Ensure that the session URL data is a valid JSON response before use * Ensure a local time in UTC is being used if the JSON data has no date * Ensure the DB is opened in the most threadsafe manner possible * Add patch provided by @phlibi to add synchronized() around DB access methods * Align timestamp creation method with itemdb if element is missing
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Describe the bug
After synchronizing the data with --sync, the process crashes with this stack:
Operating System Details
Client Installation Method
From Distribution Package
OneDrive Account Type
Business | Office365
What is your OneDrive Application Version
onedrive v2.5.0
What is your OneDrive Application Configuration
What is your 'curl' version
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
The onedrive sync folder is used for storing export data from one system and synced to a shared business folder.
Steps to reproduce the behaviour
Run onedrive with --sync --resync --resync-auth parameters
Complete Verbose Log Output
Will generate it if required and send the debug log to the mail adress because of possible sensitive data.
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: