-
Notifications
You must be signed in to change notification settings - Fork 40
fix: benchmarking logger #513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #513 +/- ##
==========================================
- Coverage 78.84% 78.77% -0.08%
==========================================
Files 99 99
Lines 23060 23081 +21
Branches 23060 23081 +21
==========================================
Hits 18181 18181
- Misses 2690 2711 +21
Partials 2189 2189
🚀 New features to boost your workflow:
|
220bbe4 to
fa9daa3
Compare
* feat: canonical command names * refactor: use types in stead of strings * refactor: telemetry * fixes * review * fix: telemetry test * fix: test, clippy * refactor: try runtime * fmt
* chore: bump versions * chore: update CHANGELOG * chore: remove deprecated flag
* feat: pop build runtime * fix: test * chore: reformat * chore: feature gating * chore: add test for collect features * feat: select runtime if multiple * chore: resolve review comments * chore: fix cargo deny * chore: clippy warnings * fix: cargo deny
AlexD10S
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix! I can now see the correct output when running pop up network -f ./network.toml, and the status still shows up properly when generating weights with pop bench pallet. Nicely done!
Initializing the logger in a global scope is not a good approach. Instead, I initialize a new logger on each new command.