The crate view page is empty when the only difference to a published crate is `-` vs `_`

[cyrgani]

Current Behavior

Documentation pages for nonexistent crates like serde-json or proc_macro2, where the only difference in the name is that _ was used but the crate name uses - (and the other way around) do not contain a 404 info (serde-json: Crate not found)
and are empty, compared to a non-existing crate that works fine.

Expected Behavior

A 404 message like for other non-existing crates or ideally also a note that a similar crate with different usage of - or _ exists.

Steps To Reproduce

1. Go to https://crates.io/crates/serde-json
2. See the (absence of the) error.

Environment

• Browser: Chrome 131.0.6778.264, Firefox 134
• OS: Linux Mint 22

Anything else?

No response

[Turbo87]

@eth3lbert could this be caused by one of your latest refactorings? the API call seems to return the right thing, but the frontend then crashes afterwards.

[eth3lbert]

Thank you for the report. I will look into this as soon as I get back to my computer.

[cyrgani]

Another case I just encountered while looking at rust-lang/cargo#2775 which causes the browser to hang and slowly causes OOM, which is probably related:
https://crates.io/crates/serde-codegen

[eth3lbert]

@eth3lbert could this be caused by one of your latest refactorings? the API call seems to return the right thing, but the frontend then crashes afterwards.

I just bisected a bit and it seems it failed at HEAD is now at bbe5345 Update dependency ember-data to v5 (#10355) 😅

After upgrading, the name requested (serde-json) and the name received (serde_json) in the response don't match, it results in another dangling crate with no versions.

Before:

After:

[Turbo87]

argh okay... I wonder if using queryRecord() instead of findRecord() would fix this 🤔

in any case, we should probably add a test case for this 😅

[eth3lbert]

I guess we could just redirect to the route with correct name?

[Turbo87]

I've opened a PR to fix it: #10369

I guess we could just redirect to the route with correct name?

unfortunately this appears to be non-trivial to implement at first glance