diagnostic: Label inference related frames#793
Merged
Conversation
Inference diagnostics with related information previously showed only the related frame signature. For attributed reports, this made it hard to tell which frame was the error origin, which frames were intermediate calls, and which frame was the analysis entry that reported the diagnostic. Carry a `RelatedFrameKind` alongside each related virtual-stack frame and prefix related-information messages with `origin:`, `via:`, or `entry:` when converting inference reports to LSP diagnostics. This keeps the existing frame signature while making the role of each related frame explicit. The change is covered by analyzer and diagnostic integration tests, and the Unreleased changelog documents the updated related-information format with an example. Co-Authored-By: GPT-5.5 <noreply@openai.com>
aviatesk
force-pushed
the
diagnostic-label-related-frames
branch
from
July 1, 2026 03:34
2162886 to
f2c66c9
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #793 +/- ##
==========================================
+ Coverage 78.29% 78.33% +0.03%
==========================================
Files 62 62
Lines 12881 12890 +9
==========================================
+ Hits 10085 10097 +12
+ Misses 2796 2793 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Inference diagnostics with related information previously showed only the related frame signature. For attributed reports, this made it hard to tell which frame was the error origin, which frames were intermediate calls, and which frame was the analysis entry that reported the diagnostic.
Carry a
RelatedFrameKindalongside each related virtual-stack frame and prefix related-information messages withorigin:,via:, orentry:when converting inference reports to LSP diagnostics. This keeps the existing frame signature while making the role of each related frame explicit.The change is covered by analyzer and diagnostic integration tests, and the Unreleased changelog documents the updated related-information format with an example.