-
Notifications
You must be signed in to change notification settings - Fork 11
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
KafkaFlow may lose an error if retry strategy fails #131
Comments
rtar
added a commit
that referenced
this issue
Dec 28, 2020
rtar
added a commit
that referenced
this issue
Dec 28, 2020
rtar
added a commit
that referenced
this issue
Dec 31, 2020
rtar
added a commit
that referenced
this issue
Jan 6, 2021
rtar
added a commit
that referenced
this issue
Jan 6, 2021
rtar
added a commit
that referenced
this issue
Jan 7, 2021
rtar
added a commit
that referenced
this issue
Jan 7, 2021
rtar
added a commit
that referenced
this issue
Jan 8, 2021
rtar
added a commit
that referenced
this issue
Jan 8, 2021
rtar
added a commit
that referenced
this issue
Jan 8, 2021
rtar
added a commit
that referenced
this issue
Jan 8, 2021
rtar
added a commit
that referenced
this issue
Jan 8, 2021
rtar
added a commit
that referenced
this issue
Jan 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
KafkaFlow may lose an error if retry strategy fails at the following line:
https://github.com/evolution-gaming/kafka-flow/blob/master/core/src/main/scala/com/evolutiongaming/kafka/flow/KafkaFlow.scala#L81
The problem is that as the
join
is never called the, if fiber dies with an error, theResource
will never be cancelled and the application will just happily hang.The text was updated successfully, but these errors were encountered: