Repository navigation
chore(deps): update a2a-sdk requirement from <0.4.0,>=0.3.4 to >=0.3.4,<1.1.0 - #1439
Merged
jonahgabriel merged 2 commits intoApr 28, 2026
Merged
Conversation
Updates the requirements on [a2a-sdk](https://github.com/a2aproject/a2a-python) to permit the latest version. - [Release notes](https://github.com/a2aproject/a2a-python/releases) - [Changelog](https://github.com/a2aproject/a2a-python/blob/main/CHANGELOG.md) - [Commits](a2aproject/a2a-python@v0.3.4...v1.0.2) --- updated-dependencies: - dependency-name: a2a-sdk dependency-version: 1.0.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
jonahgabriel
added this pull request to the merge queue
Apr 28, 2026
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 14, 2026
…ide a9f25887 Bump the omnibase-core pins (project deps + [tool.uv] override) from ==0.46.7 to ==0.46.8 and add a TEMPORARY [tool.uv.sources] git-rev override to a9f25887 -- the MERGED squash commit of core #1439 on dev (self-reports 0.46.8) -- so the terminal delegation classes (ModelDelegationCompleted/ ModelDelegationFailed) resolve before that commit is published to PyPI. uv.lock regenerated (scoped to the core source line only). Proven live on .201 stability-test (proof_class=live-readback): a fresh synthetic delegation terminalized cleanly (state=FAILED, in_flight=false, pending_emissions=NULL, terminal published to delegation-failed.v1, delegation_events projection landed). The infra defer-strand recovery (handler_wiring.py, this branch) + market emit change were verified in-image. REMOVE WHEN RELEASED: once core publishes a version containing #1439, delete the override and `uv lock`.
jonahgabriel
added a commit
that referenced
this pull request
Jul 14, 2026
…ore #1439 (#2309) * fix(OMN-14600): inline-recover the in-flight-lock defer strand + drop dead carrier arm Follow-up to OMN-14493/#2296, not a reopen. #2296 fixed the original defect (0 rows EVER reaching terminal). This closes the residual it left behind: handler_wiring.py's in-flight-lock `defer` branch (a different input arriving while a prior leg's outbox batch is committed but un-finalized) reported (1, None) -- a SUCCESS -- with the handler never run. Under a retry-storm (or simply a winner leg that crashes/stalls and never finalizes) this drops the deferred leg's own input FOREVER: no retry, no error, no DLQ, no redelivery, and the boot-time-only recovery sweep never got a second chance to clear the row within a live process. Fable-gate correction (supersedes the first fix attempt): the original design reported the defer as a conflict and relied on retry_on_optimistic_conflict exhausting and raising OptimisticConflictError to trigger a Kafka redelivery. That does NOT happen on this runtime -- the state_io stateful callback is registered as a dispatcher on MessageDispatchEngine, whose per-dispatcher invocation loop catches every exception a dispatcher raises and converts it to a returned HANDLER_ERROR status instead of re-raising. The corrected fix INLINE-RECOVERS the stalled winner's own batch (publish + finalize, from inside the deferring leg) instead of depending on redelivery. Also: the periodic recovery sweep (_ensure_stale_rows_recovered) is now interval-gated (time.monotonic(), _STATE_IO_RECOVERY_SWEEP_INTERVAL_SECONDS) instead of a one-shot boolean, so a row that goes stranded mid-process can self-heal on later traffic instead of only at the next boot/redeploy; _recover_outbox_batches isolates each row in its own try/except so one unresolvable poison row can't choke the sweep for every other row; and _legacy_delegation_envelope_unwrap heals the pre-fix ModelDelegationEventEnvelope rows still stuck in the outbox from before the OMN-14600 emit-shape fix landed (the applier's _publish_payload_for_output_event special-case tuple keeps this legacy class name for the same reason). Dropped the embedded-topic carrier-detection arm from _build_outbox_entries (and its allowed_output_topics plumbing) -- dead per the canonical two-class split executed in the companion omnimarket PR: ModelDelegationResult (and its two new subclasses) have no topic field, so there is nothing to detect. Depends on the paired omnibase_core PR (adds ModelDelegationCompleted/ ModelDelegationFailed) for the new seam tests to import; this PR carries no pyproject.toml dependency change against dev. Live-readback proof (post 3-repo fix, .201 stability-test, image ac5a9b1a0b9b): new delegation cid 86b5dcd7 reached COMPLETED/in_flight=false, terminal published, projection landed; both pre-fix stranded rows healed via the legacy-row sweep; consumer offsets +3/+3. Verify correction (non-blocking, this commit): the periodic-sweep test's single post-stall shared_cb dispatch was ALSO that closure's first-ever call, making it indistinguishable from the OLD one-shot-boolean gate (which would pass the same assertion). Added a warm-up dispatch on a third correlation before CID ever stalls, so the real probe becomes shared_cb's SECOND call -- the only dispatch that actually discriminates interval-gated re-arming from a one-shot boolean. * chore(OMN-14600): re-pin omnibase-core 0.46.7->0.46.8 + git-rev override a9f25887 Bump the omnibase-core pins (project deps + [tool.uv] override) from ==0.46.7 to ==0.46.8 and add a TEMPORARY [tool.uv.sources] git-rev override to a9f25887 -- the MERGED squash commit of core #1439 on dev (self-reports 0.46.8) -- so the terminal delegation classes (ModelDelegationCompleted/ ModelDelegationFailed) resolve before that commit is published to PyPI. uv.lock regenerated (scoped to the core source line only). Proven live on .201 stability-test (proof_class=live-readback): a fresh synthetic delegation terminalized cleanly (state=FAILED, in_flight=false, pending_emissions=NULL, terminal published to delegation-failed.v1, delegation_events projection landed). The infra defer-strand recovery (handler_wiring.py, this branch) + market emit change were verified in-image. REMOVE WHEN RELEASED: once core publishes a version containing #1439, delete the override and `uv lock`. * fix(OMN-14600): refresh infra CI contracts for core repin * fix(OMN-14600): restore runner identity lock JSON * fix(OMN-14600): unblock receipt-honesty core install --------- Co-authored-by: Test Runner <test@omninode.ai>
This was referenced Sep 6, 2026
This was referenced Sep 15, 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.
Updates the requirements on a2a-sdk to permit the latest version.
Release notes
Sourced from a2a-sdk's releases.
Changelog
Sourced from a2a-sdk's changelog.
... (truncated)
Commits
eb37091chore(main): release 1.0.2 (#1012)c24ae05fix(server): deliver push notifications across all owners (#1016)a470baetest: test push notifications in itk (#1009)cfdbe4cfeat(helpers): add non-text Part, Message, and Artifact helpers (#1004)d02ae4echore(docs): document strict AgentExecutor streaming rules in v1.0 guide (#1014)8a0f38dci(linter): show which step failed (#1013)7d197dbfix(proto): use field.label instead of is_repeated for protobuf compatibility...b3d1ad6chore(docs): update migration README.md (#1003)e3e089bchore(deps): bump cryptography from 46.0.5 to 46.0.7 (#993)237621dchore(deps-dev): bump pytest from 9.0.2 to 9.0.3 (#966)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Implements OMN-10177