fix(seer-issues-patch) More parsing of functions for Python #86558
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.
The issue-fetching query includes function names parsed out of patches so that they can be matched against event stackframes. The current suite of parsers look at the excerpt from hunk headers, probably to minimize false negatives. This misses important positives, e.g.,
component_filtered_report
is not extracted from this patch.This PR additionally extracts functions from the bodies. Precision isn't perfect, e.g,. running the parser on a patch containing a string like this—
—returns
{"not_an_actual_fxn"}
instead of{}
. But for our use cases—matching function names and file names to stackframes, and then having an LLM process issues further (as done in relevant warnings)—this trade-off is largely worth it.Currently, only Python parsing has been extended. Will see if others can be safely extended.