-
Notifications
You must be signed in to change notification settings - Fork 182
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
Collaboration utf7 ops #9505
Collaboration utf7 ops #9505
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
ecced3f
to
638cf13
Compare
3d12ebe
to
72e2af3
Compare
da67948
to
8ec0228
Compare
Failing sequence of operation is (according to the WOPI validator):
related logs:
Note that the first request gets a "CODE_TOO_EARLY" status, which isn't properly handled (we assume the error comes from a locked file, so that's why we try to get the lock.) |
The CODE_TOO_EARLY is the response code when the file is in processing. That means the backend does some virusscanning and the file is not unlocked. As the file has "just been created" that seems to be logical. In this case, we need a retry mechanism with a backoff time period. |
It seems the error wasn't triggered this time, so not sure if the last commit fixes the issue. |
The custom test cases just remove the "PutRelativeFile.IncludeHostUrls" since the collaboration service can't provide the required response easily. The rest of the test cases are the same.
76f7e01
to
8ef9bd4
Compare
fix to retry the delete operation works.
Maybe we should check the retry periods. Right now, we wait 20ms, doubling the time for each retry until a maximum of 5 seconds. Not sure what is the expected waiting time for the first retry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments.
Quality Gate passedIssues Measures |
Description
Implement the "PutRelativeFile" and "DeleteFile" and "RenameFile" WOPI operations. Some handling of utf7 is included because it's needed for the "PutRelativeFile" and "RenameFile" operation.
In addition, due to problems with the "PutRelativeFile.IncludeHostUrls" test in the WOPI validator, we'll be using a customized test case file. For now, only that test is commented out. The rest of the tests will be the same
Related Issue
no issue opened
Motivation and Context
These are one of the WOPI operations that optional
How Has This Been Tested?
Some parts manually tested using collabora as WOPI app, the rest using the WOPI validator
Screenshots (if appropriate):
Types of changes
Checklist: