-
-
Notifications
You must be signed in to change notification settings - Fork 868
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 when run synchronize due to negative free space online #2806
Comments
@KunYi Please build the client from 'source' and create a proper debug log please. To do this: When building from source, please enable debugging:
To create a debug log output, please follow:
Thanks. |
okay, I run the below steps to get the debug_output.log
|
@KunYi I am unable to reproduce this on Ubuntu 22.x using the same packages that Linux Mint 21.3 uses. I am currently installing Linux Mint 21.3. |
I rebuild v2.4.25 still work on my system
|
@KunYi So I suspect this is something very specific to your system|platform|cpu architecture. The debug log gives me some clues, I will look at a change to see if this alleviate the issue for you. |
Please can you compile the following PR which will give some further insight as to the issue you are specifically facing:
To build the PR, please follow the prior steps:
There is no need for a debug log, the following execution is all you need to do:
When running the PR, your version should be: I fully expect this to fail, but this will tell me what value this item is, which is causing your client to fail, and will then dictate the direction of the fix. |
for PR2808
|
@KunYi The root cause is that you are out of space online, however the application was not handling this correctly, which is why this was crashing for you. I was able to repeat your crash by hardcoding some values whilst developing this fix. Please can you test this in your environment. |
I rebuild and re-test on #2806 (comment) |
@KunYi When running the updated PR, your client version will be |
@abraunegg
|
|
Workaround until v2.5.1
|
…e online (#2808) * When quota["remaining"].integer is converted, if negative, this leads to an issue due to 'ulong' type being used. Update how this value is converted, and the variable type to ensure that a negative number is stored as a negative number. * Fix logging output by removing duplicate output * Align logging messages to be consistent * Fix up output alignment for '0' and 'Not Available'
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
when upgrade to latest version
and run
Operating System Details
Client Installation Method
From Distribution Package
OneDrive Account Type
Personal
What is your OneDrive Application Version
onedrive v2.5.0-1+np1+1.1
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'
~/OneDrive
What are all your local file system partition types
How do you use 'onedrive'
with windows system shared OneDrive folder, but not same time use.
Steps to reproduce the behaviour
just run 'onedrive --synchronize'
Complete Verbose Log Output
Screenshots
Other Log Information or Details
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: