-
Notifications
You must be signed in to change notification settings - Fork 126
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
ManagePage: one failed update should not cancel all updates #1656
Comments
Just a small update - the snapd API docs say:
So in principle it should be possible to refresh multiple snaps via a single API call and errors that occur during the refresh of an individual snap shouldn't affect the other ones. Example with two snaps that are up to date:
Example with two snaps, where one is currently running:
The first command creates a snap change, as expected, but the second one doesn't:
Possible workarounds
|
Confirmed with the snapd team that this is indeed expected behavior. The |
@d-loose great improvement with your latest pr!
Beside that would eventually be a little bit slower I think this would also have the advantage of seeing the progress indicators of all the snaps individually. The polkit thing is not visible for the users so I don't think this should matter that much |
If one presses update all and one of the updates can not be made because the app is running, the update all should still happen with the ones that are updateable (if this is a word)
The text was updated successfully, but these errors were encountered: