[3.1 -> 3.2] Use error log instead of warning log when resource_monitor exceeds threshold #404
Conversation
This file contains 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
[3.1] Use error log instead of warning log when resource_monitor exceeds threshold
spoonincode
approved these changes
Oct 29, 2022
This was referenced Oct 29, 2022
pnx
pushed a commit
to eosswedenorg/leap
that referenced
this pull request
Nov 22, 2022
…_3_1 Merge Main post 3 1 into Main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the resource monitor exceeds its configured threshold, log an error instead of a warning so it is clear that action is needed by the operator.
Resolves #235
Merges #400 into
release/3.1