-
Notifications
You must be signed in to change notification settings - Fork 56
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
Sporadic github action build failure fix #522
Conversation
@@ -282,6 +289,11 @@ public void close() throws Exception | |||
} | |||
} | |||
|
|||
private void drain() | |||
{ | |||
dispatchers.forEach(d -> d.drain()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dispatchers.forEach(d -> d.drain()); | |
dispatchers.forEach(DispatchAgent::drain); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also suggest we just inline this, since we don't need a separate Engine.drain()
method.
@@ -90,6 +90,8 @@ read zilla:data.ext ${kafka:matchDataEx() | |||
.build()} | |||
read "Hello, world" | |||
|
|||
read notify SENT_ABORT | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally we think of barriers as events that need to be notified because they happened, rather than naming something yet to happen in the future.
So we should rename this to reflect what has already happened here.
Suggest something like RECEIVED_SKIPPED_MESSAGE
?
@@ -73,6 +73,8 @@ write zilla:begin.ext ${kafka:beginEx() | |||
.build()} | |||
write flush | |||
|
|||
write await SENT_ABORT | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be between partition(0, 3, 3, 3)
and partition(0, 4, 4, 4)
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if I understood you correctly, it is between those two message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mean the beginEx
, referring to between the flushEx
and the dataEx
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test are failing if I put between the flushEx
and the dataEx
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, makes sense - the barrier needs to go before the flush.
@@ -73,6 +73,8 @@ write zilla:begin.ext ${kafka:beginEx() | |||
.build()} | |||
write flush | |||
|
|||
write await SENT_ABORT | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mean the beginEx
, referring to between the flushEx
and the dataEx
.
...la/specs/binding/kafka/streams/application/fetch/isolation.read.committed.aborted/client.rpt
Outdated
Show resolved
Hide resolved
@@ -73,6 +73,8 @@ write zilla:begin.ext ${kafka:beginEx() | |||
.build()} | |||
write flush | |||
|
|||
write await SENT_ABORT | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, makes sense - the barrier needs to go before the flush.
Description
Fixes #526