-
Notifications
You must be signed in to change notification settings - Fork 524
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
chore: collect static log features to a separate feature #5725
Conversation
Or we can combine |
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.
❤️
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
//! This crate is used to control static log level. |
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.
To avoid forgetting to enable the static log level in release build, how about adding a compile-time check like this?
#[cfg(all(not(feature = "enabled"), not(debug_assertions)))]
compile_error!("must enable `static-log-level` in release build with `--features static-log-level`")
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.
I'd prefer moving static-log-level and static-link in a single crate. e.g. workspace-config with enable-static-link and enable-log-level feature.
Cargo.lock
Outdated
@@ -1969,9 +1969,9 @@ checksum = "e6d5a32815ae3f33302d95fdcb2ce17862f8c65363dcfd29360480ba1001fc9c" | |||
|
|||
[[package]] | |||
name = "futures" | |||
version = "0.3.24" | |||
version = "0.3.23" |
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.
Please revert this as there's a bug in 0.3.23. 🤣 #5657 (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.
The scaling test will fail with 0.3.23
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.
LGTM. Let's see if we can make things easier after we upgrade the toolchain and use workspace inheritance in the future.
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
//! This crate is used to control static log level. |
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.
I'd prefer moving static-log-level and static-link in a single crate. e.g. workspace-config with enable-static-link and enable-log-level feature.
@BugenZhao What about now? |
LGTM. How about introducing the |
Oh, I forgot it. Let me add it. 😀 |
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.
Rest LGTM, good work!
@@ -13,3 +13,13 @@ | |||
// limitations under the License. | |||
|
|||
//! This crate includes dependencies that need to be statically-linked. | |||
#[cfg(all( |
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.
The magic of attribute combination 🤣
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.
🤣
Cargo.lock
Outdated
@@ -6708,9 +6708,9 @@ checksum = "099b7128301d285f79ddd55b9a83d5e6b9e97c92e0ea0daebee7263e932de992" | |||
|
|||
[[package]] | |||
name = "unicode-ident" | |||
version = "1.0.4" | |||
version = "1.0.3" |
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.
Would you please revert unrelated changes in Cargo.lock? Several crates have been downgraded.
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.
Sure, I'm working on it~
Codecov Report
@@ Coverage Diff @@
## main #5725 +/- ##
========================================
Coverage 75.07% 75.07%
========================================
Files 912 912
Lines 142660 142530 -130
========================================
- Hits 107098 107011 -87
+ Misses 35562 35519 -43
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
It seems that the DEBUG log of aws_config::meta::credentials::lazy_caching in the release build doesn't suppress after this PR. Have you ever try to run the cluster and see the log output? cc @MrCroxx
|
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As titled. More discussion: #5721 .
Checklist
./risedev check
(or alias,./risedev c
)Refer to a related PR or issue link (optional)
close #5721