You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracing event filtering can currently be filtered using RUST_LOG env, which is combined with our defaults (a gotcha we've stumbled on many times as you think you enabled the logs you wanted but they got silenced yet).
This is not possible for the web client as there is no concept of env. All logs >= debug are currently emitted.
It would be great to have a console or settings panel, possibly in the debugger, where you can type in a filtering directive at runtime. This would allow you to filter or enable verbose logs for only certain crates or modules, which is incredibly useful for debugging.
Tracing event filtering can currently be filtered using
RUST_LOG
env, which is combined with our defaults (a gotcha we've stumbled on many times as you think you enabled the logs you wanted but they got silenced yet).This is not possible for the web client as there is no concept of env. All logs
>= debug
are currently emitted.It would be great to have a console or settings panel, possibly in the debugger, where you can type in a filtering directive at runtime. This would allow you to filter or enable verbose logs for only certain crates or modules, which is incredibly useful for debugging.
Eliza has a similar demonstration of runtime directives that we would want to achieve: https://youtu.be/JjItsfqFIdo?t=498
The text was updated successfully, but these errors were encountered: