-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-45722: CRITICAL logs on empty quantum graph #440
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #440 +/- ##
==========================================
- Coverage 81.19% 81.15% -0.04%
==========================================
Files 96 96
Lines 10931 10937 +6
Branches 2086 2086
==========================================
+ Hits 8875 8876 +1
- Misses 1698 1703 +5
Partials 358 358 ☔ View full report in Codecov by Sentry. |
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.
Thanks for the cleanup.
The "other" category was merged with "misc" in 2022.
Critical is not an appropriate level for informational logs, especially since whether or not a failed query is truly critical (in the sense that the program cannot continue) depends on the program.
Logging a single statement as multiple logs causes problems with Loki, because each line may be rearranged or independently filtered. Logging a single multiline message fixes this problem, without changing behavior for console users. Constructing the multiline message makes it impossible to defer string evaluation, but for an error-level log this is unlikely to come up in practice.
640d5d9
to
f6f0254
Compare
This PR demotes the explanation of empty quantum graph queries from critical to error (to avoid confusion with truly fatal errors that force termination), and also merges the explanation into a single multiline log (for compatibility with JSON/Loki output).
Checklist
doc/changes