Open-EO / Open-EO/openeo-python-driver
EjrApiResponseError: improve error message
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
Context: I forgot to add a field to the EJR API so batch jobs broke; in particular, starting a batch job made OpenEO return this 500 error in response to a 400 from the EJR API:
openeo.rest.OpenEoApiError: [500] Internal: Server error: EjrApiResponseError('Error communicating with batch job system, consider trying again. Details: 400 'Bad Request' on
PATCH \'https://jobregistry.vgt.vito.be/jobs/j-2507162224414dd5ae34b7bee23d713a\': {"statusCode":400,"message":["property results_metadata_uri should not exist"],"error":"Bad Request"}') (ref: r-250716222441465198d52a399903d41c)
The error message suggests to try again but this is obviously not going to work in this case. A better approach could be to adapt this response message (and status code) to the one that we get back from the EJR API.
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 where EjrApiResponseError is created while handling the EJR API response for batch-job creation. Reproduce the shown 400 response and compare the resulting OpenEO error message and status code with the EJR response. Done means the client no longer suggests retrying for this kind of request error and exposes the relevant EJR details.
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
- 45/100