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.

Sign up for GitHub

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

Jump to bottom

[processor/memorylimiter] Check the pipeline to differentiate between refused and dropped #12463

Open
iblancasa opened this issue Feb 24, 2025 · 1 comment
Open

[processor/memorylimiter] Check the pipeline to differentiate between refused and dropped #12463

iblancasa opened this issue Feb 24, 2025 · 1 comment

Comments

@iblancasa
Copy link
Contributor 

          tangent: I wonder whether this comment (which appears 4 times now) will ever be resolved.

Originally posted by @jmacd in #12454 (comment)
@dmathieu
Copy link
Member

Original TODO:

// TODO: actually to be 100% sure that this is "refused" and not "dropped"
// it is necessary to check the pipeline to see if this is directly connected
// to a receiver (ie.: a receiver is on the call stack). For now it
// assumes that the pipeline is properly configured and a receiver is on the
// callstack and that the receiver will correctly retry the refused data again.

@dmathieu dmathieu mentioned this issue Feb 24, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dmathieu @iblancasa