ci: update prek hooks - #2
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
February 23, 2026 01:15
7c502e1 to
a237c1d
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
March 2, 2026 01:13
a237c1d to
2a6ba3a
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
March 9, 2026 01:14
2a6ba3a to
8115227
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
March 23, 2026 01:18
c0516b2 to
94f1e8f
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
March 30, 2026 01:26
94f1e8f to
f83e427
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
April 6, 2026 01:26
f83e427 to
c48c060
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
April 13, 2026 01:48
c48c060 to
64947ec
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
April 20, 2026 01:48
64947ec to
bab7987
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
April 27, 2026 01:52
bab7987 to
a789be8
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
May 4, 2026 01:56
a789be8 to
57d4130
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
May 11, 2026 02:08
57d4130 to
e639a1f
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
May 18, 2026 02:27
e639a1f to
a13ca3d
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
May 25, 2026 02:32
a13ca3d to
ce8d2f5
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
June 8, 2026 02:40
7537d3c to
e3c2051
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
June 15, 2026 02:46
e3c2051 to
75ee391
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
June 22, 2026 02:47
75ee391 to
3b2095c
Compare
tomz-alt
pushed a commit
that referenced
this pull request
Jun 22, 2026
…io#1999) Resolves the spec's §4.2 observability gap: previously, orphan-delete failures during a normal update's commit phase (when a parent's `process()` no longer declared a child it had declared on a prior run) hit the framework's default `error!` log instead of routing through the parent's user-installed exception handler chain. Only `App.drop()` (a Delete-mode root with a raising on_error) propagated descendant failures; `coco.mount`-mounted parents had no observability. Symmetric with `ComponentDeleteContext::on_error`: - `ComponentBuildContext` gains an `on_error: Option<OnError>` field. - `ComponentProcessingAction::new_build` and `new_processor_context_for_build` accept it. - `Component::mount` stores its `on_error` argument on the child's Build context (in addition to passing it to `run_in_background`) — one handler, two surfaces. - `LiveComponentController::update_full` and `run_op`'s `Op::Update` branch mirror the same pattern for the live-component dispatch path. - `App::update` (root), `Component::use_mount` (foreground), and `mount_inner_live`'s synthetic parent context pass `None` — the prior log+swallow default is preserved where intentional. `launch_child_component_gc` switches from `delete_action_on_error()` to the new unified `processing_action_on_error()`, so it cascades the parent's on_error regardless of mode. `delete_action_on_error()` stays as the Delete-only accessor used by `Component::delete`'s spawned task (a Build context's on_error is meant for cascades, not for invoking on the build's own failure — that flows through `run_in_background`'s `on_error` argument directly). Adds `test_orphan_delete_failure_routes_through_parent_handler` in test_exception_handlers.py: parent mounts child A on update #1, doesn't mount A on update #2, sink fails during the orphan delete. Verifies the handler fires exactly once (mount_kind="mount"). Toggling `launch_child_component_gc` back to `delete_action_on_error()` confirms the test fails without this change. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
July 6, 2026 02:10
2394718 to
6dc22eb
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
July 13, 2026 01:50
6dc22eb to
bb8981c
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
July 20, 2026 02:01
bb8981c to
a0f7126
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
August 3, 2026 01:52
c862563 to
0817d23
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
2 times, most recently
from
August 17, 2026 00:39
4a1a07b to
e84ede3
Compare
github-actions
Bot
force-pushed
the
prek-autoupdate
branch
from
August 24, 2026 00:40
e84ede3 to
61ee57b
Compare
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.
Automated prek hook version updates.
This PR was created by the prek autoupdate workflow.