Open-EO / Open-EO/openeo-python-client
MultiBackendJobManager: avoid mixing openEO job status and internal status in same column
Open
@HansVRP is already working on this.
Since Mar 24, 2026.
job manager
technical debt
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
MultiBackendJobManager involves a status column which is used for
- official openEO status, e.g. "created", "queued", "running", "finished", ...
- internal housekeeping e.g. "not_started", "queued_for_start"
Mixing both has popped up quite often as a source of confusion during MultiBackendJobManager feature requests, bug fixes, and attempts to improve test coverage (especially when we started to do things in threads and the order of execution stopped being deterministic)
the official job status and internal status should be separated
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.
Assessment
This issue has not been assessed yet.