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
o/snapstate/autorefresh: do not expect a valid time string in refresh.hold #13544
o/snapstate/autorefresh: do not expect a valid time string in refresh.hold #13544
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch, Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you
….hold It is possible that refresh.hold has been set to "forever" even before snapd ran for the first time. Reference: https://bugs.launchpad.net/bugs/2051917 Signed-off-by: Maciej Borzecki <maciej.borzecki@canonical.com>
a77ade3
to
522c4fc
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #13544 +/- ##
=======================================
Coverage 78.86% 78.87%
=======================================
Files 1033 1033
Lines 132065 132067 +2
=======================================
+ Hits 104159 104166 +7
+ Misses 21404 21401 -3
+ Partials 6502 6500 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was confused, "forever" is already a passed through valid value from the pov of configcore, so this is fine
@Meulengracht this can be force merged now |
It is possible that refresh.hold has been set to "forever" even before snapd ran for the first time.
Reference: https://bugs.launchpad.net/bugs/2051917