* many: repurpose quota-groups experimental feature instead of introducing a new feature flag
* cmd/snap: unhide quota commands
* cmd/snap: add missing help categories for quota commands
* features: remove feature flag from tests
* features,o/servicestate: review feedback
Clarify the docs for the quota-groups feature. Be more specific in regards to the experimental helper text. Simplify function that checks for feature flag
* features,overlord/servicestate: add support for per-quota requirements
* overlord/servicestate: add unit tests for the new per-quota requirements
* overlord/servicestate: fix doc
* tests/main/snap-logs-journal: set new experimental flag for this test
* o/servicestate: fix tests after rebase, add additional changes to spread tests after new tests have been introduced
* t/core/persistent-journal-namespace: enable experimental journal quotas
* o/servicestate: allow the old quota-groups option, remove the changes to tests as that is not needed for this PR
* o/servicestate: review feedback
spelling mistake, remove wrong return revealed by test. (but is not hit in this PR due to redundant quota checks)
* multiple: review feedback
fix unit test run
* t/m/snap-quota-journal: try again, couldn't figure out the whitespace
* features: disable refresh-app-awarness by default again
We enabled the `experimental.refresh-app-awareness` option right
before the 22.04 release [1]. However in hindsight this move was
premature. The UX is not quite ready, the refresh is stopped
but the experience should be that once the app is closed the
update gets applied which is not implemented yet. There are
also design issues with e.g. LXD as outlined in LP:#1978005
the need time and design to resolve. Another reason was the
automatic ~/snap -> ~/Snap folder migration. But this is
done differently now.
For the above reasons this commit changes the default again
to `refresh-app-awarness=false` until there is time to
fix the UX and the LXD issues.
[1] https://github.com/snapcore/snapd/pull/11566
* hookstate: disable refresh-app-awareness in gateAutoRefreshHookSuite.SetUpTest() - not strictly needed but when we enable refresh-app-awareness again it will help
* Enable refresh-app-awareness by default.
* Update tests.
* Fix comment.
* Pass --ignore-running in spread tests.
* Update hidden-snap-dir test with --ignore-running.
* Fix op-remove-retry test to kill test-snapd-tools.block process.
* Remove --ignore-running flag from hidden-snap-dir (not needed).
* Remove --ignore-running flag from refresh test (not needed).
* Add comment to the test
Co-authored-by: Maciej Borzecki <maciek.borzecki@gmail.com>
* Add comment to the test
Co-authored-by: Maciej Borzecki <maciek.borzecki@gmail.com>
* Add extra comments explaining --ignore-running use in the tests.
Co-authored-by: Maciej Borzecki <maciek.borzecki@gmail.com>
We agreed to enable this feature after a release a long while ago and
forgot about this entirely. This should improve compatibility of some
snaps that use classic confinement, as $XDG_RUNTIME_DIR will no longer
be altered, allowing unmodified binaries to find sockets and other
resources there.
Forum: https://forum.snapcraft.io/t/classic-confinement-breaks-high-dpi-support/13868
Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
This new feature flag will control the location of the per-user snap
data root. When the flag is unset, the ~/snap location is used. When
the flag is set the new ~/.snapdata location will be used as the root of
all other locations (such as SNAP_USER_DATA and SNAP_USER_COMMON).
The flag is implemented on the go and C sides, as both need to observe
it.
Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
