Allow setting RUST_LOG to any value in just all
#1016
Merged
Conversation
This file contains 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
Restioson
force-pushed
the
allow-setting-rust-log
branch
from
2857c12
to
b525cc3
Compare
Restioson
force-pushed
the
allow-setting-rust-log
branch
from
b525cc3
to
0c9a0f9
Compare
klochowicz
approved these changes
Jul 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While investigating #1004 I discovered that you can't run
RUST_LOG=warn just allsince that makes FRB codegen panic. I just overrode RUST_LOG to either debug or info depending on its actual value for the FRB codegen calls.