Skip to content
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

refactor: do not output suppressed count when it's zero #15333

Merged
merged 3 commits into from
Feb 29, 2024

Conversation

BugenZhao
Copy link
Member

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Make LogSuppressor::check returns Option<NonZeroUsize> and record the option value in tracing events. When the suppressed count is zero, the field will be omitted in the event.

Also fixed direct error formatting in mysql and postgres parser. These are corner cases that are not covered by the lints. Tracked in #15330.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Copy link
Member Author

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@@ -86,7 +89,7 @@ mod tests {
});

if let Ok(suppressed_count) = RATE_LIMITER.check() {
println!("failed to foo bar. suppressed_count = {}", suppressed_count);
println!("failed to foo bar. suppressed_count = {:?}", suppressed_count);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does the {:?} look like?

Copy link
Member Author

@BugenZhao BugenZhao Feb 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does not look good. 😄 We usually record it as a tracing field in production code. Updated the test code accordingly and it now looks like this:

image

Signed-off-by: Bugen Zhao <[email protected]>
@BugenZhao BugenZhao enabled auto-merge February 29, 2024 05:31
@BugenZhao BugenZhao added this pull request to the merge queue Feb 29, 2024
Merged via the queue into main with commit ff342fe Feb 29, 2024
27 of 28 checks passed
@BugenZhao BugenZhao deleted the bz/option-log-suppressed-count branch February 29, 2024 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants