Open-EO / Open-EO/openeo-python-driver
Support top-level run_udf in validation mode (like in wet run)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
https://github.com/Open-EO/openeo-python-driver/pull/364 added a validation error item from top-level run_udf usage:
which was ok at the time as the python client only shows this as a warning, but still allows user to submit the job.
Since https://github.com/Open-EO/openeo-web-editor/issues/309#issuecomment-3959923287 however, the web editor started blocking workflows when pre-flight validation returns errors.
This makes it impossible to submit jobs involving top-level run_udf nodes through web editor
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 in openeo_driver/ProcessGraphDeserializer.py at lines 1792-1793 and compare validation-mode handling of top-level run_udf with its wet-run behavior. Reproduce a workflow containing a top-level run_udf node and verify that pre-flight validation no longer returns an error that blocks submission through the web editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100