Open-EO / Open-EO/openeo-python-client
Auto-retry as batch when sync processing fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
When synchronous processing fails (e.g. with ProcessGraphComplexity) the client could optionally retry with a batch job
First step is probably to harmonize result handling for sync and batch jobs (e.g. see #240 )
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 reading issue #240 and tracing how synchronous results and batch-job results are currently handled in the Python client. Identify the existing processing entry points and determine the intended behavior for retrying failures such as ProcessGraphComplexity. Done means the sync and batch result handling is harmonized and optional fallback retry behavior is specified and covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100