We've noticed that the API seems to be sporadically returning HTTP 202 responses which are not being handled when using query_iterative() which is hard coded not to retry requests. Unfortunately it's difficult to reproduce this problem without running a bunch of lookups. We are doing a series of queries by ORCID that look like this:
search publications where researchers.orcid_id = "0000-0001-7334-8049"
return publications[basics + book + altmetric + date + doi + funders + open_access + pmcid + pmid + times_cited + abstract + altmetric_id + issn + isbn + publisher + recent_citations + supporting_grant_ids + concepts]
limit 25 skip 0
Has something changed in the service API where HTTP 202 responses (with no body) are being returned? Is this something that perhaps a retry and then throwing a suitable exception will help solve?
If you are interested more details can be found in this issue: sul-dlss/rialto-airflow#821
We've noticed that the API seems to be sporadically returning HTTP 202 responses which are not being handled when using
query_iterative()which is hard coded not to retry requests. Unfortunately it's difficult to reproduce this problem without running a bunch of lookups. We are doing a series of queries by ORCID that look like this:Has something changed in the service API where HTTP 202 responses (with no body) are being returned? Is this something that perhaps a retry and then throwing a suitable exception will help solve?
If you are interested more details can be found in this issue: sul-dlss/rialto-airflow#821