Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @cjgillot (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
cjgillot
left a comment
There was a problem hiding this comment.
r=me with one nit.
TBH, I had trouble to use this debug tracing of queries: difficult to filter and drowning in some return values, HIR in particular. How do you use it?
There was a problem hiding this comment.
Could you move this to the call site of call_provider?
Yea, return values can be annoying. I mostly log to a file and then just skip over the bad parts 🙃 wrt filtering: I filter queries to specific arguments by filtering on the debug representation of the |
|
fwiw: I am looking into how to generally work with logs in a more reasonable scheme than "have a log file and grep through it". I want to start dumping json logs and then figure out some UI (possibly just a terminal UI for working with tracing logs specifically) that can actually fold nested calls instead of just indenting them |
|
@bors r=cjgillot |
Make queries traceable again This can't be tested without something along the lines of rust-lang#111924 unfortunately. We could benchmark turning query tracing into an `info` level tracing statement, but let's get this fix landed first so we can actually debug properly again
…llaumeGomez Rollup of 7 pull requests Successful merges: - rust-lang#99587 (Document memory orderings of `thread::{park, unpark}`) - rust-lang#112836 ([rustdoc] partially fix invalid files creation) - rust-lang#112853 (Add `lazy_type_alias` feature gate) - rust-lang#112863 (Fix copy-paste typo in `eprint(ln)` docs) - rust-lang#112883 (Make queries traceable again) - rust-lang#112885 (Fix msg passed to span_bug) - rust-lang#112886 (Revert 'Rename profile=user to profile=dist') r? `@ghost` `@rustbot` modify labels: rollup
This can't be tested without something along the lines of #111924 unfortunately.
We could benchmark turning query tracing into an
infolevel tracing statement, but let's get this fix landed first so we can actually debug properly again