Skip to main content

Module pending_shutdown

Module pending_shutdown 

Source

Structs§

Entry 🔒
PendingClearedEvent
agent:shutdown-pending-cleared: the request ended, and how.
PendingView
A request as the caller and the frontend see it (§12.2).
RemoteRequest
A request opened on another AgentMux instance on this machine (a cross-channel FleetBulkStop target, whose user is asked there): where its status lives. status for these is proxied (see remote_for).

Enums§

Action
What happens if the user lets the window run out.

Constants§

EVENT_SHUTDOWN_PENDING
EVENT_SHUTDOWN_PENDING_CLEARED
KEEP_FINISHED_MS 🔒
Finished requests stay answerable this long, then are dropped.
OVERRIDE_WINDOW

Statics§

ENTRIES 🔒
REMOTE 🔒

Functions§

active_for
The request for this block still waiting on the user or already under way, if any.
audit 🔒
The outcome, once per requester, each as its own source (§6.5 step 8).
audit_note
The request-time audit note: whether this caller opened the window or joined someone else’s.
begin 🔒
pending → proceeding, atomically, handing over the action to run: exactly one of the window running out and the user’s Keep running wins (ReAgent P1 on #3789 — checking and setting under separate locks let a late check see pending after a keep).
cleared 🔒
covers_of 🔒
Every block a request covers; empty once it’s forgotten.
entries 🔒
is_active 🔒
keep
“Keep running” (§12.3). kept_by_user if the request was still pending, too_late if the shutdown had already begun (or it isn’t this block’s).
notify_router 🔒
prune 🔒
publish_pending 🔒
agent:shutdown-pending for view, to the pane at block_id.
remember_remote
Remember that request_id lives on the instance at local_url.
remote_for
The instance a forwarded request lives on, if it is one.
request
Ask to shut block_id down, subject to the user’s override. A request already pending — or under way — for the block is joined instead: the clock never restarts, and no second window opens beside it (ReAgent P1 on #3789: a second banner’s Keep running could not stop the first). A joiner whose action does more (see Action::rank) replaces the pending action and is named on the banner, so nobody is told the outcome of less than they asked for (ReAgent P1 on #3798). The returned view says whose request it is: a caller whose by/via differ has joined someone else’s.
request_within 🔒
run_action 🔒
set_status 🔒
status