Repository navigation
fix: observe the final partial bulk dispatch chunk - #40
Merged
Merged
Conversation
This was referenced Oct 4, 2026
elpete
marked this pull request as ready for review
October 4, 2026 09:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When bulkDispatch ends with a partial chunk, it calls the provider directly and skips onCBQJobPublished/onCBQJobPublishException. Route that chunk through the same publish-result boundary as complete chunks so its jobs are observed and provider failures are rethrown unchanged. Preserve the existing provider pushMany call even when the trailing bulk chunk contains one job.
Add regressions for successful and rejected final chunks. All 13 focused observation/bulk-dispatch specs pass on BoxLang 1.18.0 and Lucee 6.2.8.20; formatting checks pass for all 57 files. This follows the merged #39; documentation and the 7.0.1 coverage boundary are in ortus-docs/cbq-docs#1.
CI validation at 5a06ee8: the push workflow passes on all five stable engines (Lucee 5/6 and Adobe 2021/2023/2025), including formatting. The Lucee 5 full suite reports 105 passed, zero failures/errors, and one existing skip. The duplicate pull-request workflow also passes every test and formatting job.