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 have a situation in which multiple requests start simultaneously and cascade new requests on their own.
Because of the initial small requests, loading-bar gets to 100% within a second. Within 500ms of completing the request, new calls are fired away, which actually take most of the time. The progress bar however does not reset or reflect work to be done: it just stays on 100% until finally the last requests are finished. In effect the prograss bar is stuck at 100% almost at the beginning for several seconds.
One solution it to keep setting the progress, even in the 'request' function around line 94:
return{'request': function(config){if(!config.ignoreLoadingBar&&!isCached(config)){if(reqsTotal===0){cfpLoadingBar.start();}reqsTotal++;cfpLoadingBar.set(reqsCompleted/reqsTotal);// added this line}returnconfig;},
The downside of this is it does not take into account the previous requests being completed: it just starts over.
The text was updated successfully, but these errors were encountered:
I have a situation in which multiple requests start simultaneously and cascade new requests on their own.
Because of the initial small requests, loading-bar gets to 100% within a second. Within 500ms of completing the request, new calls are fired away, which actually take most of the time. The progress bar however does not reset or reflect work to be done: it just stays on 100% until finally the last requests are finished. In effect the prograss bar is stuck at 100% almost at the beginning for several seconds.
One solution it to keep setting the progress, even in the 'request' function around line 94:
The downside of this is it does not take into account the previous requests being completed: it just starts over.
The text was updated successfully, but these errors were encountered: