Conversation
…ings Replace the deeply nested else-if chain for rate-limit retries in the live stream tick loop with a clean retry loop with backoff. The old structure also silently swallowed non-rate-limit errors on the first attempt. Add doc comments to all functions and types missing them across streamdl.go, download_stream.go, grpc_client.go, config.go, config_reader.go, and move_file.go. Closes #555 Closes #554
…ocstrings fix: rate-limit retry loop and docstring coverage
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 4 minutes and 41 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Major release merging staging into master, covering work since the last production release.
Features
vod: true,vod_limit), SQLite tracking database, atomic claim/complete/fail lifecycle, and yt-dlp-based VOD enumeration (feat: Twitch VOD support #551, closes [FEATURE] - Twitch VOD Support #231)/healthon both client and server containersBug Fixes
getStreamcallurlsmap withsync.RWMutexto prevent concurrent map accessChores
Test plan
go build ./...passesgo test ./...passes (90s, all green)