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

Fixed check for pseudo-release. #4833

Merged

Conversation

jamesharding
Copy link
Contributor

The 'status' field is potentially null, and in this case the dictionary key is not returned by the API. Using get will return null in this case. Tested locally and this solves the issue!

Description

Fixes #4832.

The 'status' field is potentially null, and in this case the dictionary key it is not returned by the API. Using get will return null in this case. Tested locally and this solves the issue!
@sampsyo
Copy link
Member

sampsyo commented Jun 29, 2023

Thanks!! Looks like this was introduced in #4714. @TypicalFence, could you please take a look? It would be really useful to add a test here that reflects all the kinds of data that can might be missing to make sure we don't make the same mistake again.

@sampsyo sampsyo merged commit 99f641c into beetbox:master Jun 29, 2023
14 checks passed
@jamesharding jamesharding deleted the jamesharding-pseudo-release-patch branch June 29, 2023 15:38
@TypicalFence
Copy link
Contributor

@sampsyo someone submitted another pr (#4834) fixing this and they've included a test for that case. Maybe you could merge that one instead of me writing something from scratch?

@sampsyo
Copy link
Member

sampsyo commented Jul 3, 2023

Indeed; thanks for the heads up, @TypicalFence!

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

Successfully merging this pull request may close these issues.

KeyError in new pseudo-release extraction path
3 participants