-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Entries being lost in notebooks #6675
Comments
Might be possible with a restart to Apache if you already have a notebook open. |
I’m able to reproduce by doing the following: With two instances of chrome open (one chrome, one chromium):
|
I've found the issue, it's related to transactions. I don't know exactly how users are getting the application into this state (although I have found one reliable reproduction path), but once they do it's difficult to recover. Here's how I reproduced it. It's probably not how users are doing it in production, but hopefully enough for us to fix it.
|
Although I can reproduce this issue using the above steps in version 2.2.0 of Open MCT in our VIPER MMOC environment, I cannot reproduce it in 3.0.0 snapshot. Closing to retest. |
Testing InstructionsFollow reproduction steps in #6675 (comment) and verify that the issue cannot be reproduced. |
I'm not able to reproduce step #4 where the entry section at the top is disabled. |
Cannot reproduce. Fixed(?) |
throttled network and tried to stress the network by opening several instances of the map tool. could not reproduce loss of entries. |
Summary
Multiple users have reported losing notebook entries. The notebook entries appear to be added but upon navigating away and back the entries are gone. These issues have been observed even in notebooks that only have a single concurrent user, open in a single tab, suggesting that this is not a persistence conflict.
The persistence call to save a notebook entry could be getting backed up behind other pending requests and is never successfully persisted. Aside from reducing the number of requests overall, this could be improved by providing better user feedback, like an activity indicator that shows when an entry is saving. We should also prevent a user from adding additional entries when a persistence operation is taking place, this will highlight to the user sooner that a problem has occurred and reduce the amount of work lost.
There may also be some as-yet unknown issue with persisting notebook entries.
Steps to Reproduce
Exact steps are unknown at this point. Try adding entries to a single-user notebook with heavy network throttling in place.
Environment
Impact Check List
The text was updated successfully, but these errors were encountered: