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

[component] component.go - review ErrNilNextConsumer #9322

Closed
atoulme opened this issue Jan 20, 2024 · 0 comments · Fixed by #9779
Closed

[component] component.go - review ErrNilNextConsumer #9322

atoulme opened this issue Jan 20, 2024 · 0 comments · Fixed by #9779

Comments

@atoulme
Copy link
Contributor

atoulme commented Jan 20, 2024

ErrNilNextConsumer is an error exposed by the component package.

In what situations can this error actually be thrown, ie, when is the next consumer ever nil?
Would it be possible to do away with this error? Would it make sense to have a check before the component is initialized instead?

dmitryax pushed a commit to open-telemetry/opentelemetry-collector-contrib that referenced this issue Mar 19, 2024
**Description:**
Remove explicit checks in all receivers to check if the next consumer is
nil.
The nil check is now done by the pipeline builder.

This is a follow up of
open-telemetry/opentelemetry-collector#9322.

This PR blocks
open-telemetry/opentelemetry-collector#9779.
dmitryax pushed a commit that referenced this issue Mar 20, 2024
**Description:** 
Remove deprecated error `ErrNilNextConsumer`

**Link to tracking Issue:**
Fixes #9322
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants