Skip to content

fix: shutdown drain can hang when downloadStream exits without response send#584

Merged
cursor[bot] merged 2 commits into
stagingfrom
fix/shutdown-drain-hang-583
Jul 6, 2026
Merged

fix: shutdown drain can hang when downloadStream exits without response send#584
cursor[bot] merged 2 commits into
stagingfrom
fix/shutdown-drain-hang-583

Conversation

@biodrone

@biodrone biodrone commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace the shutdown response channel drain with a downloadWg WaitGroup, matching the existing vodWg / postScriptWg pattern
  • Remove the unused response parameter and SIGINT-only sends from downloadStream
  • Add a unit test documenting the WaitGroup shutdown pattern

Fixes #583

Test plan

  • go test ./...
  • Send SIGINT while multiple live downloads are active and confirm the process exits promptly
  • Send SIGINT while one stream ends naturally at the same moment and confirm no hang

Made with Cursor

Shutdown could hang when a live download exited naturally or failed after
SIGINT because the drain loop expected response sends that only happened
on explicit interrupt paths.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@biodrone, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b1b1dec7-b9e8-4592-b5e9-d7a5b79a5042

📥 Commits

Reviewing files that changed from the base of the PR and between f499951 and 5bb2704.

📒 Files selected for processing (4)
  • download_stream.go
  • shutdown_test.go
  • streamdl.go
  • tests/integration/.gitignore
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/shutdown-drain-hang-583

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

The docker-compose VOD SQLite mount writes runtime state under
tests/integration/data/ that should not be tracked.

Co-authored-by: Cursor <cursoragent@cursor.com>
@cursor cursor Bot merged commit e234285 into staging Jul 6, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant