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

Bug fix #71

Merged
merged 1 commit into from
Feb 8, 2024
Merged

Bug fix #71

merged 1 commit into from
Feb 8, 2024

Conversation

realalanc
Copy link
Contributor

bug_presence As for some Uniprot id, there is no suitable gene name, so when running line 163, it gets a 200 OK, but when running into line 165, it gets no key 'geneName', so raises KeyError The very first uniprot id identified is A0A1D6EIG7, I tried getting json by my browser and read the website of this id, the problem consists. As far as I know, many other genes correspond this situation. It can be seen that, the 'geneName' key is in absence. Similarly, we also need to check the existence of the key 'gene' in the same line 165. Also, in line 170, the name 'uniprot_id' is not defined, it may be 'uniprot_accession_number' instead?

As for some Uniprot id, there is no suitable gene name, so when running line 163, it gets a 200 OK, but when running into  line 165, it gets no key 'geneName', so raises KeyError
The very first uniprot id identified is A0A1D6EIG7, I tried getting json by my browser and read the website of this id, the problem consists.
As far as I know, many other genes correspond this situation.
Similarly,  we also need to check the existence of the key 'gene' in the same line 165.
Also, in line 170, the name 'uniprot_id' is not defined, it may be 'uniprot_accession_number' instead?
@DegnKristine
Copy link
Contributor

Thank you very much for identifying this challenge and the suggestion to solve it.

@DegnKristine DegnKristine merged commit e0aa40e into ELELAB:main Feb 8, 2024
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.

2 participants