fix: batch network requests in fetchAudio
#102
Merged
Conversation
This file contains 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.
I decided to set my device on fire by asking Crunker to concatenate about 2800 mp3 files into one wav.
Crunker was fine to do this, but Chrome refused and failed some of the network requests, rather understandably.
To work around
ERR::INSUFFICIENT_RESOURCES, I have implemented a batching mechanism intofetchAudioso Crunker will only attempt to fetch 200 files at any one time. This worked fine in my browser on the same set of 2800 files.(For anyone wondering, the resulting WAV file was about 256 MB.)