Open-EO / Open-EO/openeo-python-driver
get results of "error"ed job: return 424 iso 400 JobNotFinished
Open
Nobody has claimed this yet.
API
bug
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
>>> con.get("/jobs/j-1001f917bab34ef1aeefd460e329d0e1").json()["status"]
"error"
>>> r = con.get("/jobs/j-1001f917bab34ef1aeefd460e329d0e1/results", check_error=False)
>>> (r, r.json())
(<Response [400]>,
{'code': 'JobNotFinished',
'id': 'r-047b9e98c45148acb52d812eb0694400',
'message': 'Batch job has not finished computing the results yet. Please try again later or contact our support.'})
per spec, should be HTTP 424, with:
The request can't be fulfilled as the batch job failed. This request will deliver the last error message that was produced by the batch job.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the implementation of the GET /jobs/{job_id}/results endpoint and how it handles jobs with status "error". Reproduce the reported request, then verify that the response uses HTTP 424, code JobNotFinished, and delivers the last error message produced by the batch job as required by the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100