Skip to content

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Oct 8, 2020

latestStableVersion is already guaranteed to be null because of the previous condition. I assume the original intention here was to check for latestUnyankedVersion instead.

It looks like this bug was already present in the original implementation in #1857

r? @jtgeibel

`latestStableVersion` is already guaranteed to be `null` because of the previous condition. I assume the original intention here was to check for `latestUnyankedVersion` instead.
@jtgeibel
Copy link
Member

jtgeibel commented Oct 9, 2020

Good catch. @bors r+

@bors
Copy link
Contributor

bors commented Oct 9, 2020

📌 Commit 66a1cc4 has been approved by jtgeibel

@bors
Copy link
Contributor

bors commented Oct 9, 2020

⌛ Testing commit 66a1cc4 with merge 380a2e1...

@bors
Copy link
Contributor

bors commented Oct 9, 2020

☀️ Test successful - checks-travis
Approved by: jtgeibel
Pushing 380a2e1 to master...

@bors bors merged commit 380a2e1 into rust-lang:master Oct 9, 2020
@Turbo87 Turbo87 deleted the unyanked-bug branch October 9, 2020 11:54
jtgeibel added a commit to jtgeibel/crates.io that referenced this pull request Oct 29, 2020
It looks like fixing the bug in rust-lang#2894 exposed this bug. When there are
only pre-release versions of a crate, the version number needs to be
extracted so that the version object can be located again a few lines
later. This could probably be refactored, but for now this removes the
spurious error notification shown in the UI.
bors added a commit that referenced this pull request Oct 29, 2020
Fix version logic when there are only pre-releases

It looks like fixing the bug in #2894 exposed this bug. When there are
only pre-release versions of a crate, the version number needs to be
extracted so that the version object can be located again a few lines
later. This could probably be refactored, but for now this removes the
spurious error notification shown in the UI.

r? `@Turbo87`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend 🐹 C-bug 🐞 Category: unintended, undesired behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants