Repository navigation
Conversation
Read ordinary file lock metadata from the final remote properties together with the remote file ID. Clear obsolete cached locks when the server reports an unlocked file and retain current remote lock ownership. Assisted-by: Codex:GPT-6 Signed-off-by: Li Wei <caeser222000@sohu.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After an upload, the final PROPFIND updates the cached remote file ID but leaves its previous ordinary file lock metadata in place. Refresh the lock flag, owner, type, timestamps and token from that same response, including clearing cached fields when the server reports the file as unlocked.
Regression tests cover unchanged and replaced remote IDs, a current lock owned by another editor, an unlocked response, and preservation of local file identity and storage paths. This change does not alter E2EE directory tokens or upload request headers.
Validation:
AI assistance: Codex (GPT-6) assisted with implementation, regression tests and validation. The contributor authorized the DCO sign-off.