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(error): eliminate usage of DisplayErrorContext #15225

Merged
merged 2 commits into from
Feb 27, 2024

Conversation

BugenZhao
Copy link
Member

@BugenZhao BugenZhao commented Feb 23, 2024

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

What's changed and what's your intention?

Eliminate usages of DisplayErrorContext, which is similar to thiserror_ext::Report. Several reasons:

  • Report/DisplayErrorContext should only be used when printing the entire error at the top level. For the Display implementation of an error type, the best practice is not to include the Display of the source chain.
  • Report strips the common suffix of errors' Display implementation to make it clean, while DisplayErrorContext does not.
  • DisplayErrorContext attaches a Debug view of the error after formatting the error source chain. This makes the result verbose, not composable, and not able to be cleaned up by Report.

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.

@BugenZhao BugenZhao marked this pull request as ready for review February 23, 2024 08:58
@BugenZhao BugenZhao marked this pull request as draft February 23, 2024 08:59
@BugenZhao BugenZhao force-pushed the bz/format-error-lint-anyhow-error branch from 8670b57 to 39e5a2a Compare February 23, 2024 09:26
Base automatically changed from bz/format-error-lint-anyhow-error to main February 23, 2024 10:04
Signed-off-by: Bugen Zhao <i@bugenzhao.com>
@BugenZhao BugenZhao marked this pull request as ready for review February 26, 2024 09:10
@@ -106,10 +105,8 @@ impl Sink for KinesisSink {
.stream_name(&self.config.common.stream_name)
.send()
.await
.map_err(|e| {
tracing::warn!("failed to list shards: {}", DisplayErrorContext(&e));
Copy link
Member Author

Choose a reason for hiding this comment

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

There should be a principle that "whoever handles the error is responsible for logging the error". The error here is thrown and should be handled (or logged) by the caller.

@BugenZhao BugenZhao enabled auto-merge February 27, 2024 08:02
@BugenZhao BugenZhao added this pull request to the merge queue Feb 27, 2024
Merged via the queue into main with commit 2157ed6 Feb 27, 2024
27 of 28 checks passed
@BugenZhao BugenZhao deleted the bz/only-format-self branch February 27, 2024 09:00
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.

3 participants