Repository navigation
0.1.7: four uploads at once for each server, up from two - #4
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The upload queue now works on 4 uploads at once for each server, up from the SDK's default of 2 (`QueueOptions.threads`). A lane is per server, so every system uploading to the same Rdio Scanner shares its workers: at about 4800 calls an hour, 2 workers leave each upload, audio included, about 1.5 s before calls start to queue and arrive late.
This is the same change as trunk-plugin-broadcastify#4 and trunk-plugin-openmhz#7. The SDK default is unchanged.
`cargo test` passes and clippy has no warnings.
🤖 Generated with Claude Code