logging functionality to socketio added and configured testing for critical erros #1966
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
joernu76
reviewed
Aug 31, 2023
pytest.ini
Outdated
| log_format = %(asctime)s %(levelname)s %(message)s | ||
| log_date_format = %Y-%m-%d %H:%M:%S | ||
| log_cli = 1 | ||
| log_cli_level = CRITICAL |
joernu76
approved these changes
Aug 31, 2023
ReimarBauer
added a commit
that referenced
this pull request
Sep 6, 2023
…itical erros (#1966) * logging functionality to socketio added and configured testing for critical errors * updated to ERROR
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.
Purpose of PR?:
Fixes #1965
Does this PR introduce a breaking change?
needs additional config vars in the server config
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Does this PR results in some Documentation changes?
If yes, include the list of Documentation changes
Checklist:
<type>: <subject>