Closed kayzzen01 closed 6 months ago
@kayzzen01
I don't know how the innards of OneDrive work, but perhaps after the consistency and integrity check period I should reread this queue.
This queue is read.
The entire client has been re-written over the last 12 months. To understand the architecture of the client please read: https://github.com/abraunegg/onedrive/blob/onedrive-v2.5.0-release-candidate-1/docs/client-architecture.md
Wow, what a huge job was done, amazing. The documentation is so rich.
Sorry, my lack of knowledge.
I can't say I understood all the flows in such a short time. I didn't see when the application sends it to the queue. This is controlled by the syncStatus property, that is, when the application detects a change, both local and remote, is the syncStatus updated? Because it should be safer to work with pseudo queues saved in the database.
Is this architecture valid for version 2.4.25? Or is it precisely the changes that are in version 2.5.0 that will bring more reliability?
All of that documentation is specific to v2.5.0 and above
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
During the "Performing a database consistency and integrity check on locally stored data due to fullscan requirement" period, OneDrive does not synchronize. From what I understand, it even detects the change and puts it in a queue, because after the OneDrive service is restarted it synchronizes these changes.
I don't know how the innards of OneDrive work, but perhaps after the consistency and integrity check period I should reread this queue.
Operating System Details
Client Installation Method
From Source
OneDrive Account Type
Personal
What is your OneDrive Application Version
onedrive v2.4.25
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'
I use OneDrive in monitor mode and as a service:
systemctl --user enable onedrive
Steps to reproduce the behaviour
Wait for Performing a database consistency and integrity check on locally stored data due to fullscan requirement to start and change a file. After finishing the verification, the file will not be synchronized.
Restart the service for the file to be synchronized:
systemctl --user restart onedrive
Complete Verbose Log Output
I once renamed a file during the integrity check period and the error below was caused.
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response