Repository navigation
fix: retry UniProt ID-mapping jobs on error code 50 - #15
Merged
iquasere merged 1 commit intoOct 26, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Hi! While I was using UPIMAPI to annotate metagenomic bins I occasionally encountered a UniProt server-side error that caused the annotation to stall in the UPIMAPI job.
When UniProt marks an asynchronous ID-mapping job as failed, its status endpoint can return HTTP 400 with
jobStatus: "ERROR"and error code 50. Becauserequests.get()returns this as a response rather than raising an exception,get_url()did not increment its retry counter or leave the loop. It consequently kept requesting the status of the same failed job, which could never recover.Solution
This change identifies server-side failures from general HTTP 5xx responses and terminal UniProt responses containing
jobStatus: "ERROR"with error code 50.These responses raise a dedicated
UniProtServerError. To prevent a UniProt-side failure from stopping the entire UPIMAPI run, the ID-mapping batch functions catch this error and submit the same chunk again, producing a new job ID instead of continuing to poll the failed job. Fresh submissions are limited by the existing--max-triessetting, preventing another infinite retry loop. Other HTTP errors continue to propagate normally and do not trigger a new submission.I performed local tests covering the observed code-50 response and the fix appears to work as intended.