Skip to content

Stop Chromecast discovery when the connect times out - #309

Merged
balloob merged 1 commit into
Sendspin:mainfrom
balloobbot:chromecast-timeout-discovery
Oct 26, 2026
Merged

balloob merged 1 commit into
Sendspin:mainfrom
balloobbot:chromecast-timeout-discovery

Conversation

@balloobbot

@balloobbot balloobbot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

What does this implement/fix?

When the Chromecast connect timed out, its discovery kept running for the life of the process. The timeout path now stops discovery. Minimal version of the fix by @kiwipaulrob.

Related issue (if applicable):

Types of changes

  • Bugfix (non-breaking change which fixes an issue): bugfix
  • New feature (non-breaking change which adds functionality): new-feature
  • Enhancement to an existing feature: enhancement
  • Breaking change (changes CLI options, settings, hooks or the protocol in a way that is not backwards compatible): breaking-change
  • Refactor (no behavior change): refactor
  • Documentation only: documentation
  • Maintenance / chore: maintenance
  • CI / workflow change: ci
  • Dependencies bump: dependencies

🤖 Generated with Claude Code

The timeout around the blocking Chromecast connect cannot cancel the
executor thread. When cast.wait() hangs, the thread never reaches its
finally block, so the zeroconf browser keeps running for the life of
the process. Stop discovery from the timeout path.

Co-authored-by: Paul Robertson <paularobertson@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the bugfix Fixes a bug label Oct 26, 2026
@balloob
balloob merged commit 752a90f into Sendspin:main Oct 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Fixes a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants