Repository navigation
Expose publish outcomes and explicit worker attempt boundaries - #39
Merged
Merged
Conversation
elpete
marked this pull request as ready for review
October 4, 2026 07:53
This was referenced Oct 4, 2026
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
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.
Observability integrations can observe publish results and each immutable execution attempt, establish context on the actual worker, and restore it when that worker exits. Completion callbacks carry the same execution ID even when a timeout finishes before the worker exits.
Observer failures and the existing recovery diagnostics now use a shared LogBox warning path with a short stderr fallback if logging also fails. All seven empty catches in the models are removed. Diagnostic failures preserve enqueue results, job outcomes, terminal-failure attempts, and completion-hook cleanup.
CFFormat 0.22.1 was reproduced adding a space before unquoted struct-key colons on each pass. CI pins the stable 0.21.0 version and checks formatting without creating automatic commits, preventing the repeated workflow approval cycle. The four affected files have been normalized.
The asynchronous observation test converts the concurrent Java queue snapshot to a CFML array before using member functions. SQL compilation tests use an isolated provider so PostgreSQL/SQL Server builders never leak into database teardown.
Validation: both push and pull-request workflows pass at 89fb36a. Each of Lucee 5, Lucee 6, Adobe 2021, Adobe 2023, and Adobe 2025 reports 103 passed, zero failures/errors, and one existing skip. Both formatting jobs pass. Locally, the two affected suites pass 13/13 on Lucee 6.2.8.20 and Adobe 2023.0.25+330977; the six queue observation specs also pass on BoxLang 1.18.0. All 57 project files pass formatting, two successive formatter passes are stable, and an unformatted directory fixture is rejected.
The preview supports the Sentry observability integration. BoxLang full-suite compatibility and the comprehensive Sentry acceptance scenarios remain separate verification boundaries.
Documentation: ortus-docs/cbq-docs#1 covers the six new hooks, statuses, context propagation and restoration, timeout ordering, idempotent completion, diagnostics, and CFML/native BoxLang examples. The docs are marked unreleased.
A separate follow-up, #40, covers publish-result observations for the final partial bulk chunk. That correction is not part of this merged PR or release 7.0.1; the documentation states the coverage boundary.