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
So far I still don't reproduce it consistently. But I did reproduce it once, and in executeNextRequest() the nested condition probably evaluated to false. Now we need to figure out why.
I reproduce this better when throttling at 64 kbps.
The scenario is that the last xxforms-upload-progress event is in progress just at the time the upload response completes. So the executeNextRequest() for xxforms-server-events finds Globals.requestInProgress == true, which is expected.
However, once xxforms-upload-progress completes, it should check the queue again, but it doesn't.
The reason is that we set Globals.requestInProgress = false as a side-effect of running Support.fetchText, but our Future's onComplete which actually handles the Ajax response runs before that side-effect. So it sees Globals.requestInProgress == true still.
The order of onComplete is not guaranteed. We could use andThen instead.
To reproduce, the key is to have a very slow connection to maximize the chances that the xxforms-upload-progress will overlap the end of the upload. A single upload control is enough to reproduce.
I finally reproduced this locally using throttling:
But I don't always reproduce it.
+1 from customer
The text was updated successfully, but these errors were encountered: