Open-EO / Open-EO/openeo-python-driver
Job with many results: read timeout on metadata
@EmileSonneveld is already working on this.
Since Feb 11, 2026.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
So one LCFM job has this read timeout on result metadata, the job generated many results:
url = '/openeo/1.2/jobs/j-26013001053549dc9fbe27b7f0c25299/results
https://jenkins.vgt.vito.be/job/openEO/job/openeo-apex-benchmarks/418/testReport/junit/tests/test_b…
https://openeo-admin.vgt.vito.be/job/j-26013001053549dc9fbe27b7f0c25299
Not a blocker, but requires further investigation:
Does request time increase with size of the result? Do we need different timeout?
What about stac 1.1 codepath, is that better?
Anything we can fix? (But avoiding deep dive into 1.0 codepaths...)
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.