Spinner doesn't go away until you log off for 33K or more CVRs (in Chrome)
Verbal description from CDOS: at 33K CVRs the spinner doesn’t go away until you log off, or until the state starts the audit.
[We expect to receive a more carefully documented description, with screenshots, by the end of the week.]
See Test Case #5, in https://drive.google.com/open?id=0B5_BzTbq3XxPYUVhVnNSaEZQOGs
@sfsinger19103, I can't reproduce this locally. I think the problem is just that it is taking a long time to process the CVR export file, and the users are not getting progress indication other than the spinner. Regardless, this isn't a client bug, unless we can reproduce a case where (1) the CVR export upload_and_ import succeeded per the server logs, but (2) the client is still stuck in a spinner state.
Note: I tested the case where I manually interrupt the backend import processing, causing a network failure. As expected, the spinner disappears, the CVR export form resets to its initial state, and the user gets an error message.
Closing unless someone can repro.
CDOS is still observing this bug in their environment. Reopening while we help identify a repro and fix.
This was auto-closed; reopening until we confirm that this is fixed for CDOS.