-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rust: Implement database quality telemetry query #18697
Conversation
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.
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more
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.
C# LGTM
@@ -0,0 +1,46 @@ | |||
/** |
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.
We already have a rust/ql/src/queries/diagnostics
and rust/ql/src/queries/summary
directory and this introduces rust/ql/src/queries/telemetry
as well. Are the new queries meaningfully different enough to justify a third location or should we condense back down to (any) two of them?
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.
I simply followed the same structure that we have for Java and C#.
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.
OK, I'll look into whether I can combine any of these directories after this PR is merged. Don't really want a proliferation of folders unless they're meaningfully different.
MacroCallTargetStatsReport::numberOfOk(key, value) or | ||
MacroCallTargetStatsReport::numberOfNotOk(key, value) or | ||
MacroCallTargetStatsReport::percentageOfOk(key, value) | ||
) and |
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.
There's quite a bit of overlap with rust/summary/summary-statistics
(files and lines of code extracted), the focus is a little different here but something to be aware of.
/* -Infinity */ | ||
value != -1.0 / 0.0 and | ||
/* NaN */ | ||
value != 0.0 / 0.0 |
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.
This is hurting my maths brain, but it does seem to be the way float
works. :(
DCA LGTM, I can see the new "Missing call targets, per source" |
Co-authored-by: Geoffrey White <[email protected]>
For now, this will yield DCA numbers on missing call targets, but should also eventually yield telemetry data.