Skip to content

docs: name both new IRR-CA anchors in the SoundDispatchOutcome docstring #1269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jleinenbach merged 1 commit into from
Sep 4, 2026
Merged

docs: name both new IRR-CA anchors in the SoundDispatchOutcome docstring #1269

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions custom_components/googlefindmy/const.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,17 @@ class SoundDispatchOutcome(StrEnum):

Only ``TRANSPORT_FAILED`` justifies a push cooldown. Only ``ACCEPTED`` proves
that the credentials worked.

See IRR-CA-SOUND-FAILURE-CLASS in ``docs/PLAY_SOUND_ARCHITECTURE.md`` for the
per-member "may a caller arm a push cooldown" table this type carries, and
IRR-CA-STOP-BREAKS-SELF-INFLICTED-COOLDOWN for the qualifier on the stop
path. There the readiness gate lets a stop through a running window when the
stop carries our own fresh cancel key, so a window armed by a play cannot
lock out a stop this integration can correlate; and when such a stop then
fails on the transport, the cooldown is reported through
``_note_stop_transport_problem_without_extending()``, which puts a window
that was already running back instead of restarting it, so a stop cannot
feed the window it just broke through.
"""

ACCEPTED = "accepted"
Expand Down
Loading