[better_errors] Refactor more uses of pe.tracing_debug_info (part 3) #26100
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.
We replace uses of
pe.tracing_debug_info
with withapi_util.tracing_debug_info
,which uses the actual args and kwargs, instead of
in_tree
to manufacture fakeargs and kwargs. This ends up being more accurate, especially for
arg_names
;see changes in debug_info_tests.py.
This means that we have to construct the debug info further upstream, before
flattening args. This will later help populate debug info in
WrappedFun
andJaxpr
.This is part 3 of a series (following #26097, #26099) for jit, checkify, custom_dce.