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

Firefox: Image upload is back to being stuck after hitting 100% #1709

Closed
askfongjojo opened this issue Jul 29, 2023 · 3 comments
Closed

Firefox: Image upload is back to being stuck after hitting 100% #1709

askfongjojo opened this issue Jul 29, 2023 · 3 comments
Milestone

Comments

@askfongjojo
Copy link

In the latest rack2 build, I was unable to import images on Firefox. It stopped progressing after hitting 100% bulk-write completion:
image
I saw this error on the browser console which may be unrelated:
image

I'm retrying the upload (for the third time) and watching the network tab. Will add more information if it reveals something useful.

@askfongjojo askfongjojo added this to the 1.0.2 milestone Jul 29, 2023
@askfongjojo askfongjojo changed the title Firefox: Image upload is back to being stuck (and rollbacked) at 100% Firefox: Image upload is back to being stuck after hitting 100% Jul 29, 2023
@david-crespo
Copy link
Collaborator

Yes, I think the console error is unrelated.

The Omicron issue is still open oxidecomputer/omicron#3559 and there’s a related Dropshot issue oxidecomputer/dropshot#726 that it looks like we’re ready to move forward on. The Dropshot thing might be good for me to take a look at because I’m low on urgent tasks.

@david-crespo
Copy link
Collaborator

david-crespo commented Jul 29, 2023

The presentation we always saw in the network tab was that one or more of the chunk POSTs would just hang forever with no info available when you click on it.

@askfongjojo
Copy link
Author

The upload succeeded on the 3rd try (though it ended with an unrelated error with disk deletion). Since I didn't encounter this issue in the last two weeks, I thought I should log this just in case it's caused by some other changes. I'm closing this as a duplicate of the open issues mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants