Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not crash on inaccurate progress reporting #1521

Merged
merged 5 commits into from
Mar 4, 2019

Conversation

chanseokoh
Copy link
Member

Fixes #1512 (comment), where the root cause is believed to be an inaccurate or missing Content-Length value. (The log shows that remainingAllocationUnits is -1 when the Verify statement is violated.)

Closes #1512.

@chanseokoh chanseokoh merged commit b18bc6a into master Mar 4, 2019
@chanseokoh chanseokoh deleted the i1512-no-crash-on-inaccurate-progress branch March 4, 2019 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants