-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
onDownloadProgress
changed after 1.6.8
#6417
Comments
Hi, I can confirm that rolling back to 1.6.8 fixes the issue. |
I confirm I have the same problem with version 1.7.2 on Firefox. |
Same issue starting from 1.7.0-beta.0 using `onUploadProgress. Also the frequency of |
I have same problem in chrome when i use onUploadProgress, axios version is 1.7.2. |
We're also having the same issue on version 1.7.2. Any known (hot)fix for this issue 🙏? |
Describe the bug
It appears that, starting from 1.7.0,
onDownloadProgress
's event doesn't fully complete: seems like the callback is not called upon the very last chunk. In fact, I use the event to expose the file transfer's percentage and it never reaches the 100%. It always stops between 98 and 99, but this problem never occurs with <= 1.6.8.To Reproduce
Apologies, I cannot provide the URL to the 13 MB file, but here's the code and the output for 1.6.8 and 1.7.0+:
This is what the console logs up to 1.6.8...
...and this is what logs from 1.7.0 on:
Code snippet
No response
Expected behavior
No response
Axios Version
1.7.0+
Adapter Version
No response
Browser
No response
Browser Version
No response
Node.js Version
No response
OS
No response
Additional Library Versions
No response
Additional context/Screenshots
No response
The text was updated successfully, but these errors were encountered: