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
ocasional panic #4
Labels
Comments
Thanks. I guess warning and retrying after a small timeout is probably the best thing to do in most cases? We could do that as first measure, then add special casing for various http 4xx and 5xx codes later. |
johanhelsing
added
bug
Something isn't working
good first issue
Good for newcomers
labels
Sep 20, 2022
Sounds perfect! I guess it depends on the status code as to if it’s
sensible to retry.
…On Tue, 20 Sep 2022 at 08:01, Johan Klokkhammer Helsing < ***@***.***> wrote:
Thanks. I guess warning and retrying after a small timeout is probably the
best thing to do in most cases?
We could do that as first measure, then add special casing for various
http 4xx and 5xx codes later.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGEJCA6JC3W43TNSEH232TV7FONJANCNFSM6AAAAAAQQXRU6U>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
johanhelsing
added a commit
that referenced
this issue
Sep 23, 2022
Instead warn before reporting the asset as NotFound, same as we do on native. Ideally, we'd handle the actual errors, but this makes the two implementation behave similarly at least. Fixes: #4
This was referenced Sep 23, 2022
I fixed the panic at least. Don't have time to look into retrying now, but created new issues for that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The unwrap here is causing a panic occasionally:
bevy_web_asset/src/web_asset_io.rs
Line 26 in d4cd4f4
The text was updated successfully, but these errors were encountered: