Repository navigation
Footage: a file over the video host's 30 GB limit fails at once, saying so - #65
Merged
Merged
Conversation
…ng so
It used to wait on Google Drive, and the panel promised it would come in
within a day: when Drive let it through, the video host refused it
("MaxFileSizeError"). Its size is known before anything is pulled, from the
whole-file answer or the one-byte range a refused file still serves, so a
file over the limit now fails with "37.6 GB is over the video host's 30 GB
limit". Retrying it works once the limit is raised.
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
1 participant
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.
A file over the video host's 30 GB limit used to wait on Google Drive, and the footage panel said importing would carry on "usually within a day". It could not: once Drive let it through, the video host refused it with
MaxFileSizeError.Its size is known before anything is pulled: from the whole-file answer (
content-length), or from the one-byte range a file Drive is refusing still serves. A file over the limit now fails at once with a plain reason, e.g. "37.6 GB is over the video host's 30 GB limit". It is never handed to the video host, and the Drive-wait banner no longer counts it. Retrying it works once the limit is raised (MAX_RELAY_BYTES).agent.mdsays so.