Fix panic when decoding

[NobodyXu]

Fix #298

[NobodyXu]

cc @Turbo87 Can you try this PR please?
It should fix the error you've encountered.

[Turbo87]

just pushed it to our staging environment. it'll take a while to verify that it's actually fixed, but thanks for the very quick response! ❤️

[robjtede]

lgtm but we can wait for til EoD to release in case @Turbo87 reports any issues

[Turbo87]

I pushed Turbo87/crates.io@e6431c9 to our staging environment, but Sentry shows:

which seems to indicate that the issue still exists or I've messed up the update 😅

[NobodyXu]

Hmmm the branch is auto deleted since it is merged to main.

Maybe you need to use the main branch, or the latest commit hash?

[Turbo87]

yeah, though when I did the commit the branch was not merged yet and the lockfile includes the commit hash. since you're using proper, non-squash merges here the commit hash should still be resolvable by cargo.

but just in case I'll update it to main and try again 👍

[NobodyXu]

the lockfile includes the commit hash.

Well hmmm I don't know if it would works because I never tried.

Thanks for the retry, let's see if it would fix the issue

[Turbo87]

I changed it over to Turbo87/crates.io@c58174f, but according to Sentry it's still happening with this deployment too :-/

[NobodyXu]

Thanks, is there any unwinding/panic info?

[Turbo87]

basically all I can see is the stacktrace and a bit of metadata, but nothing else related to the panic.

I just deployed rust-lang/crates.io#9639 to the staging environment to double check and that did indeed "fix" the issue for now.