Added recognition and support for event log level#943
Merged
Conversation
Switched to soft restriction for log level event feature
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
1 participant
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.
Fix Failure due to Event Log Level
Issue: N/A
Python Version(s) Tested: 3.14.3
Operating System(s): Ubuntu 25.10
📝 Summary
During testing it was identified that the new support for Events to have a log level was causing failures due to there now being an additional
log_levelfield which was not yet recognised by the API.🔍 Diagnosis
If applicable, please summarise any information relating to how the bug was identified, and the root causes.
🔄 Changes
log_levelmember toEventSetmodel class.log_leveltoRun.log_eventin User API.✔️ Checklist