-
Notifications
You must be signed in to change notification settings - Fork 638
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
fix: never drop responses during batch processing #11865
Conversation
Since we never returned 'false' from `tryWriteResponse`, the retry logic was useless. This changes the return type to void to indicate that we can't tell if sending the response was successful or not.
During batch processing, multiple responses can accumulate, for example when using create process instance with result. Previously, this was not handled correctly. The last response was the only one being sent out. Now we buffer all responses and send them all out together.
28cec90
to
11cf8b4
Compare
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.
🚄
bors r+
Test Results 997 files ± 0 997 suites ±0 1h 48m 15s ⏱️ + 9m 37s Results for commit 11cf8b4. ± Comparison against base commit c757d7b. This pull request removes 412 and adds 620 tests. Note that renamed tests count towards both.
|
Build succeeded: |
Backport failed for Please cherry-pick the changes locally. git fetch origin stable/8.1
git worktree add -d .worktree/backport-11865-to-stable/8.1 origin/stable/8.1
cd .worktree/backport-11865-to-stable/8.1
git checkout -b backport-11865-to-stable/8.1
ancref=$(git merge-base c757d7b865a3ecd0e38f11869f82a07040d768a5 11cf8b466e25b8d65f9878a28a46b5572f9d5da4)
git cherry-pick -x $ancref..11cf8b466e25b8d65f9878a28a46b5572f9d5da4 |
11867: [Backport 8.1] fix: never drop responses during batch processing r=oleschoenburg a=Zelldon ## Description Backported #11865, had to fix several merge conflict related to structural changes which have been done on main, but not on 8.1 Had to fix another test, because this was removed on main, but still exists on 8.1 [test: adjust test case](aae1a80) <!-- Please explain the changes you made here. --> ## Related issues <!-- Which issues are closed by this PR or are related --> closes #11848 Co-authored-by: Ole Schönburg <ole.schoenburg@gmail.com> Co-authored-by: Christopher Zell <zelldon91@googlemail.com>
Description
During batch processing the stream processor now accumulates multiple responses and sends them out together.
Keeping only one response was not correct in some situations, for example when using
CreateProcessInstanceWithResponse
when the process ends with a service task or message event.Related issues
closes #11848