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

redpanda: hexdump config on 'unknown escape character' #8552

Merged
merged 1 commit into from
Feb 1, 2023

Conversation

jcsp
Copy link
Contributor

@jcsp jcsp commented Feb 1, 2023

On this particular exception type (but not on general config load errors), dump out a hexdump-style view of the bytes we loaded from the config yaml file.

This error occurs very occasionally, it is suspected that something is wrong with lower layers in the system, but it's hard to infer much without knowing what's in the byte buffer that we're reading.

Related: #3798

Backports Required

  • none - not a bug fix
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v22.3.x
  • v22.2.x
  • v22.1.x

UX Changes

None

Release Notes

Improvements

On this particular exception type (but not on general config load
errors), dump out a hexdump-style view of the bytes we loaded
from the config yaml file.

This error occurs very occasionally, it is suspected that something
is wrong with lower layers in the system, but it's hard to
infer much without knowing what's in the byte buffer
that we're reading.

Related: redpanda-data#3798
Copy link
Contributor

@andijcr andijcr left a comment

Choose a reason for hiding this comment

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

lgtm

@jcsp
Copy link
Contributor Author

jcsp commented Feb 1, 2023

@jcsp jcsp merged commit 0006570 into redpanda-data:dev Feb 1, 2023
@jcsp jcsp deleted the issue-3798-debug branch February 1, 2023 21:08
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