fix(collector) add nil check before consuming traces in telemetryAPIReceiver#2241
Merged
wpessers merged 1 commit intoopen-telemetry:mainfrom Apr 9, 2026
Conversation
herin049
approved these changes
Apr 9, 2026
herin049
force-pushed
the
fix/collector/nil-check-receiver-next-traces
branch
from
2d366d9 to
de38dae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In case the collector is configured without a traces pipeline this currently results in a panic since
r.nextTraceswould always be nil. This regression was accidentally introduced in #2066 and was missed during review.