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

All stream processors must have err outport #861

Open
emil14 opened this issue Feb 2, 2025 · 0 comments
Open

All stream processors must have err outport #861

emil14 opened this issue Feb 2, 2025 · 0 comments
Labels

Comments

@emil14
Copy link
Collaborator

emil14 commented Feb 2, 2025

At the moment stream processors like For/Map/Filter/Reduce doesn't have err outport and there's no way to interrupt stream processing (not to be confused with #666 - that is about interruption of stream generation). Also no way to properly handle error that was thrown from stream-processor's handler.

  1. Implement errors.Lift and errors.Must that can convert between nodes that have err and those that doesn't have that
  2. Update stream iterators and examples/tests that depends on them
  • stream-processor can't stop stream from generating, (that's exactly what 666 is about) but it can (and should) stop processing next stream items. We probably gonna need to implement state package first, so this might be a separate task. For beginning we need to simply propagate errors to parent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant