promoted bad memory_limit check from warning to error as it may break updater#24717
Merged
promoted bad memory_limit check from warning to error as it may break updater#24717
Conversation
blizzz
requested review from
ChristophWurst,
MorrisJobke,
nickvergessen,
rullzer and
weeman1337
blizzz
changed the title
kesselb
approved these changes
Dec 15, 2020
nickvergessen
approved these changes
Dec 15, 2020
blizzz
added
4. to release
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
blizzz
force-pushed
the
enh/noid/memory_limit_to_error
branch
from
0a2f12b to
1995097
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cf. nextcloud/updater#316
I might not sure why admins would ignore orange message, but not red messages… but maybe it helps 🍀