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

Retries #13

Open
ghost opened this issue Jul 15, 2019 · 2 comments
Open

Retries #13

ghost opened this issue Jul 15, 2019 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ghost
Copy link

ghost commented Jul 15, 2019

It would be more robust if the javascript code on the front-end part (re)tried again after an XMLHttpRequest() failure.

That'd be useful in particuler when running Django's built-in webserver on http://localhost:8000 (using manage.py runserver) because when in development mode (DEBUG=1) Django's builtin webserver reloads python source files that change by restarting the webserver and the short unavailability of the webserver makes the progressbar stop (I'm using the default refresh rate of 500ms).

Thank you.

@czue
Copy link
Owner

czue commented Jul 15, 2019

thanks this makes sense to me. would love a patch if you are willing to put one together!

@OmarWKH
Copy link
Collaborator

OmarWKH commented Oct 6, 2020

This can be done now by overriding onNetworkError. I'm not sure if it should be default behaviour or left to the user.

Alternatively, the user could be allowed to handle this exception/promise rejection (currently they can't):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants