feat: Update: Logging with "tracing" #216
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
FroVolod
force-pushed
the
tracing-for-log
branch
from
d59e776
to
597b0b3
Compare
|
@FroVolod Thank you for your contribution! Your pull request is now a part of the Race of Sloths! Current status: executed
Your contribution is much appreciated with a final score of 5! Another weekly streak completed, well done @FroVolod! To keep your weekly streak and get another bonus make pull request next week! Looking forward to see you in race-of-sloths What is the Race of SlothsRace of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow For contributors:
For maintainers:
Feel free to check our website for additional details! Bot commands
|
added 2 commits
September 11, 2024 20:24
FroVolod
force-pushed
the
tracing-for-log
branch
from
b00baf0
to
65fc0f0
Compare
frol
approved these changes
Sep 11, 2024
Merged
frol
added a commit
that referenced
this pull request
Sep 13, 2024
## 🤖 New release * `cargo-near`: 0.8.2 -> 0.9.0 * `cargo-near-build`: 0.1.0 -> 0.1.1 <details><summary><i><b>Changelog</b></i></summary><p> ## `cargo-near` <blockquote> ## [0.9.0](cargo-near-v0.8.2...cargo-near-v0.9.0) - 2024-09-12 ### Added - Fixed GitHub CI staging workflow generated by `cargo near new` command to work correctly with docker case ([#193](#193)) - Extracted cargo-near-build into a standalone crate to be able to use it in near-workspaces and other places without the rest of the heavy dependencies of cargo-near ([#198](#198)) - Added tracking of `cargo near new` usage to collect statistics of the command usage ([#192](#192)) ### Fixed - Addressed warnings in `cargo build -p cargo-near-build` cmd in releaze-plz flow ([#212](#212)) ### Other - Updated near-* dependencies to 0.26 release ([#220](#220)) - Use "tracing" for logging and loading indicators ([#216](#216)) - update docker image and sdk version in `cargo near new` template ([#218](#218)) - [**breaking**] updates near-* packages to 0.25 version. Updates near-sdk to 5.4 ([#215](#215)) </blockquote> ## `cargo-near-build` <blockquote> ## [0.1.1](cargo-near-build-v0.1.0...cargo-near-build-v0.1.1) - 2024-09-12 ### Added - Fixed GitHub CI staging workflow generated by `cargo near new` command to work correctly with docker case ([#193](#193)) ### Other - Use "tracing" for logging and loading indicators ([#216](#216)) - fix clippy ([#219](#219)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/MarcoIeni/release-plz/).
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.
This is preparation for the implementation of the TEACH ME mode.
Command with
RUST_LOG=info:Command with
RUST_LOG=trace: