-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Lost the app_settings, presumably during a failed kujua-lite update #386
Comments
Well you would still be left with the app_settings on the previous revision (39). The update process replicates the new ddoc in and then updates the app_settings property based on the previous revision. The right thing to do in case of failing to update the app_setting property is to revert the ddoc update (in this case back to revision 39). |
Is it updating twice here? |
Pretty sure it is, by design. Once to replicate the new ddoc, once to update the app_settings property. I don't see anything wrong with that per se, except for better error handling. BTW, this is a dashboard issue and we should probably open an issue there if we want it changed... https://github.com/garden20/dashboard |
I'm trying to think if we could solve these sorts of conflict issues generically, perhaps inside of a form renderer. There are similar failures (but not data-loss issues) when multiple updates to the same user happen in _rewrite/users. Dave |
I'm not sure if that's the same issue. But what might help is to serialize the ajax calls per UI so one ajax async call doesn't overwrite another? Maybe something like https://github.com/gnarf/jquery-ajaxQueue. |
Also just looked at the dashboard issue tracker and found this item garden20/dashboard#42 So I think this also describes the problem of not being able to update after manually pushing, I think that is a pretty important one too. We should probably add some comments there to upvote if we thinks it's important to fix. I would argue it's probably more important than this issue (app_settings update error handling or supporting revert). |
History of issue for posterity:
The text was updated successfully, but these errors were encountered: