Skip to content
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

Conflict resolution is not working in multi-user notebooks #5921

Closed
3 of 7 tasks
akhenry opened this issue Oct 27, 2022 · 4 comments · Fixed by #6067
Closed
3 of 7 tasks

Conflict resolution is not working in multi-user notebooks #5921

akhenry opened this issue Oct 27, 2022 · 4 comments · Fixed by #6067
Labels
bug:regression It used to work. Now it doesn't :( needs:e2e Needs an e2e test severity:critical type:bug

Comments

@akhenry
Copy link
Contributor

akhenry commented Oct 27, 2022

Summary

When two users make conflicting changes to a notebook the notebook plugin will detect the conflict and attempt to merge the changes from the two users.

Expected vs Current Behavior

Adding two different entries at the same time should result in both entries appearing in the notebook with no errors shown to the user.

Steps to Reproduce

  1. Open a notebook in Chrome
  2. Open the same notebook in Firefox
  3. In the Chrome network tab throttle the network connection down to slow 3d
  4. Add an entry to the notebook in Chrome
  5. Quickly jump over the Firefox and add an entry there.

Observe that an error is displayed to the user, and the entry made in Firefox appears in Chrome.

Environment

  • Open MCT Version: 2.1.2
  • Deployment Type: VIPER Dev

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@michaelrogers
Copy link
Contributor

michaelrogers commented Nov 17, 2022

409 Conflicts still appear when testing multi-user notebooks. @jvigliotta and myself tested this during testathon 10/17/2022.

@unlikelyzero
Copy link
Collaborator

Testing Notes

Test on 2.1.4.ERT and 2.1.5

@ozyx
Copy link
Member

ozyx commented Dec 29, 2022

Testathon 12/29/22:

Verified on 2.1.5 and 2.1.4-ERT.

One thing I did notice is that the timestamp on the entry is the time the entry was initiated, but not when it was persisted. This can lead to some confusion, but sorting does put the entries in the correct order in terms of when they were persisted.

@akhenry
Copy link
Contributor Author

akhenry commented Jan 5, 2023

the timestamp on the entry is the time the entry was initiated, but not when it was persisted

Good point. There have been arguments both ways on this one. We will respond to real-world feedback and adjust accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:regression It used to work. Now it doesn't :( needs:e2e Needs an e2e test severity:critical type:bug
Projects
Development

Successfully merging a pull request may close this issue.

5 participants