daemon, o/snapstate: implement snapstate.InstallPath in terms of refresh#17166
daemon, o/snapstate: implement snapstate.InstallPath in terms of refresh#17166andrewphelpsj wants to merge 2 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #17166 +/- ##
==========================================
- Coverage 79.12% 79.12% -0.01%
==========================================
Files 1385 1388 +3
Lines 193310 193402 +92
Branches 2466 2466
==========================================
+ Hits 152954 153020 +66
- Misses 31165 31185 +20
- Partials 9191 9197 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Thu Jun 11 18:42:06 UTC 2026 Failures:Preparing:
Executing:
Restoring:
Skipped tests from snapd-testing-skipIf you wish to have any of the below tests run in your PR, in your PR description, add 'unskip:' followed by a copy-and-pasted list (without variants) of the below tests you wish to run (unskip plus test list must be valid yaml)
|
0894708 to
5b7a043
Compare
pedronis
left a comment
There was a problem hiding this comment.
behavior and symmetry question
| // Note that the state must be locked by the caller. | ||
| // The provided SideInfo can contain just a name which results in a | ||
| // local revision and sideloading, or full metadata in which case it | ||
| // the snap will appear as installed from the store. |
There was a problem hiding this comment.
the comment here probably needs to explain the behavioral differences between this and InstallOne with PathInstallGoal or maybe the issue is that we want InstallOne with that to also do the right thing?
There was a problem hiding this comment.
I'll update the comment on the differences, though I'm not clear on what we want InstallOne with that to also do the right thing might mean?
Do you mean that we should consider making that trigger a seed-refresh?
This lets us use the existing seed-refresh implementation for free during single-path installation. Tests are added for this behavior.
5b7a043 to
cf03f3b
Compare
will need to be reviewed from scratch
This lets us use the existing seed-refresh implementation for free during single-path installation. Tests are added for this behavior.