You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected curl to output only 10 lines a second, but instead it output almost 4K lines a second. Note that this seems to happen only when the Content-Length header is not given, (which seems to be the case if you request a tarball from GitHub that hasn't been requested in a while, I suggest asking for rc1 tarballs of the Linux kernel, they don't seem to be downloaded very often, but once you download it, the Content-Length header will be provided for a short time afterward) which also seems to explain why the progress bar is locked at 100% all the time.
I did this
I expected the following
I expected
curl
to output only 10 lines a second, but instead it output almost 4K lines a second. Note that this seems to happen only when theContent-Length
header is not given, (which seems to be the case if you request a tarball from GitHub that hasn't been requested in a while, I suggest asking forrc1
tarballs of the Linux kernel, they don't seem to be downloaded very often, but once you download it, theContent-Length
header will be provided for a short time afterward) which also seems to explain why the progress bar is locked at 100% all the time.curl/libcurl version
operating system
ElementaryOS Loki (based on Ubuntu 16.04)
Other thoughts
My best guess is that this is because the progress "done" callback is getting called multiple times due to the
Content-Length
not being known.The text was updated successfully, but these errors were encountered: