-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add trace-level logging for Metadata API operations #2538
base: main
Are you sure you want to change the base?
Conversation
Test Results 7 files ±0 7 suites ±0 2m 48s ⏱️ - 1m 30s Results for commit fbaf6df. ± Comparison against base commit 7377bf3. This pull request removes 2 tests.
♻️ This comment has been updated with latest results. |
@@ -84,7 +85,7 @@ async fn delete_key( | |||
} | |||
|
|||
// todo(azmy): implement both PreconditionHeader and VersionHeader | |||
// as extractors after updating axium to version > 0.8 | |||
// as extractors after updating axum to version > 0.8 |
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.
// as extractors after updating axum to version > 0.8 | |
// as extractors after updating axum to version > 0.8 |
key, | ||
version, | ||
precondition, | ||
String::from_utf8_lossy(&value), |
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 am wondering if the value should be printed in the trace logs. it's probably not an issue during testing but in general this can be big and also binary. Maybe drop the value from the logs and just print the len of it. This can save us a .clone()
as well of the value.
Ok(value) => trace!( | ||
"Get key: {:?} -> value: {} @{}", | ||
key, | ||
String::from_utf8_lossy(&value.value), |
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.
Same thought over having the value in the logs here.
Trivial change to aid in understanding distributed test runs.