Skip to content

Conversation

@max-nextcloud
Copy link
Collaborator

📝 Summary

  • Fixes Resolving conflicts is slow #4075.
  • Speed up the sync for one request AFTER the force save. Otherwise the PollingBackend will poll only once every 5 seconds when only one user is connected.
  • The $syncService.startSync() had no effect as it tried to reconnect an already connected backend.

🏁 Checklist

  • Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
  • Sign-off message is added to all commits
  • Tests end to end tests are fixed with this commit as it prevents timeouts.
  • Documentation is not required

@max-nextcloud
Copy link
Collaborator Author

/backport 8114c69 to stable26

@cypress
Copy link

cypress bot commented Apr 24, 2023

3 flaky tests on run #9494 ↗︎

0 142 1 0 Flakiness 3

Details:

fix(conflict): resolve quickly with fast sync.
Project: Text Commit: 697a14adc5
Status: Passed Duration: 04:20 💡
Started: Apr 25, 2023 6:49 AM Ended: Apr 25, 2023 6:54 AM
Flakiness  sync.spec.js • 1 flaky test

View Output Video

Test Artifacts
Sync > recovers from a lost connection Output Screenshots
Flakiness  share.spec.js • 1 flaky test

View Output Video

Test Artifacts
Open test.md in viewer > Share a file with download disabled shows an error Output Screenshots
Flakiness  conflict.spec.js • 1 flaky test

View Output Video

Test Artifacts
Open test.md in viewer > resolves conflict using server version Output Screenshots

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.

Copy link
Member

@juliusknorr juliusknorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice one 👍

@juliusknorr juliusknorr added bug Something isn't working 4. to release labels Apr 25, 2023
Fixes #4075.

* Speed up the sync for one request AFTER the force save.
  Otherwise the `PollingBackend` will poll only once every 5 seconds
  when only one user is connected.
* The `$syncService.startSync()` had no effect
  as it tried to reconnect an already connected backend.

Signed-off-by: Max <[email protected]>
@max-nextcloud max-nextcloud force-pushed the perf/fast-conflict-resolution branch from 8114c69 to 4a7106c Compare April 25, 2023 06:35
@max-nextcloud
Copy link
Collaborator Author

/compile

Signed-off-by: nextcloud-command <[email protected]>
@max-nextcloud max-nextcloud merged commit e0bc12d into main Apr 25, 2023
@delete-merged-branch delete-merged-branch bot deleted the perf/fast-conflict-resolution branch April 25, 2023 07:17
@backportbot-nextcloud
Copy link

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin/stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Resolving conflicts is slow

4 participants