-
Notifications
You must be signed in to change notification settings - Fork 931
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
core: Listener.handleNewSignedBlock doesn't correctly record any errors to trace span #3814
Labels
Comments
github-actions
bot
added
needs:triage
external
Issues created by non node team members
labels
Oct 5, 2024
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Oct 6, 2024
…us from returned error or panics This change ensures that if a panic occurs, that span.RecordError correctly records it and then if an error is returned that span.Status correctly captures and records it. Fixes celestiaorg#3814
I have mailed out PR #3817 |
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Oct 7, 2024
…us from returned error or panics This change ensures that if a panic occurs, that span.RecordError correctly records it and then if an error is returned that span.Status correctly captures and records it. Fixes celestiaorg#3814
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Oct 7, 2024
…us from returned error or panics This change ensures that if a panic occurs, that span.RecordError correctly records it and then if an error is returned that span.Status correctly captures and records it. Fixes celestiaorg#3814
odeke-em
added a commit
to orijtech/celestia-node
that referenced
this issue
Oct 7, 2024
…us from returned error or panics This change ensures that if a panic occurs, that span.RecordError correctly records it and then if an error is returned that span.Status correctly captures and records it. Fixes celestiaorg#3814
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we look at the code in this function
celestia-node/core/listener.go
Lines 223 to 271 in 896a46b
in no place is the returned error intercepted and recorded on the span.
Remedy
Go supports named returns as a first class feature and that can be used to fix this problem simply by
/cc @cristaloleg @Wondertan @liamsi
The text was updated successfully, but these errors were encountered: