Remote changes to notebooks not being reflected in real-time

[akhenry]

Summary

AKA "multi-user notebook doesn't work any more".

Expected vs Current Behavior

When multiple users are viewing a notebook, changes by one users should be automatically reflected in other user's views. For example, when one user adds a new entry, all users viewing that page should see that entry appear automatically. This used to work but it appears that a recent code change has introduced a regression here.

Steps to Reproduce

1. Using an instance of Open MCT with Couch DB as the persistence backend
2. Open a notebook in Firefox (or Safari)
3. Open the same notebook in Chrome. It's important to use two different browsers as the Couch synchronization uses a shared worker to reduce the number of server connections we are holding open.
4. Add a new entry in Firefox.
5. Observe that the new entry does not automatically appear in Chrome.

Environment

• Open MCT Version: c10e9ad
• Deployment Type: VIPER test and local dev with Couch DB enabled

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

[akhenry]

Test Instructions

1. Execute reproduction steps above and verify that remote changes to notebook entries are automatically reflect
2. Add and remove tags and verify that changes are automatically reflected for other users (using the same two browser method from step 1.

[jvigliotta]

Verified Fixed: Testathon 8/2/22

[ozyx]

Verified Testathon 8/2/22:

I was able to create entries on Chrome and Firefox instances and they appeared in the other, synchronized. Edits, and deletes were also reflected across browser instances.

[akhenry]

Reopening, this regression was again observed in recent demo of 2.0.7

[jvigliotta]

Was unable to replicate this issue again, needs retesting.

[jvigliotta]

Verified Fixed - Testathon 9/12/22 (Without Tags, will update, with tags)