This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Log when events are (unexpectedly) filtered out of responses in tests #14213
Merged
MadLittleMods
merged 8 commits into
develop
from
madlittlemods/unexpected-filtered-event-logging-in-tests
Jun 2, 2023
Merged
Changes from 6 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c6aec96
Log when events are filtered out of responses in tests
MadLittleMods 9c5b13a
Merge branch 'develop' into madlittlemods/unexpected-filtered-event-l…
MadLittleMods aa64946
Log in trial tests
MadLittleMods 7168a26
Log in complement
MadLittleMods bdd8f83
Add changelog
MadLittleMods 0e0cefb
Fix logs in complement
MadLittleMods 5d93e91
Merge branch 'develop' into madlittlemods/unexpected-filtered-event-l…
MadLittleMods 3f37966
Only enable extra logs for developers looking for more INFO
MadLittleMods File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Log when events are (maybe unexpectedly) filtered out of responses in tests. |
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -54,4 +54,10 @@ def setup_logging() -> None: | |||||
log_level = os.environ.get("SYNAPSE_TEST_LOG_LEVEL", "ERROR") | ||||||
root_logger.setLevel(log_level) | ||||||
|
||||||
# Log when events are (maybe unexpectedly) filtered out of responses in tests. It's | ||||||
# just nice to be able to look at the CI log and figure out why an event isn't being | ||||||
# returned. | ||||||
logging.getLogger("synapse.visibility.filtered_event_debug").setLevel(logging.DEBUG) | ||||||
MadLittleMods marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
# Blow away the pyo3-log cache so that it reloads the configuration. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This comment is just copied from synapse/synapse/config/logger.py Lines 300 to 301 in 703a8f9
|
||||||
reset_logging_config() |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove
SYNAPSE_LOG_SENSITIVE
in favor ofSYNAPSE_LOG_TESTING
here?The docs around
SYNAPSE_LOG_SENSITIVE
already mention it's for "a developer attempting to debug something particularly tricky."Are we worried about a deprecation period in this case? If it's only a developer thing, I don't think we need to worry about it at all.