Open-EO / Open-EO/openeo-python-client
More compact job progress report in jupyter
Open
@ElienVandermaesenVITO is already working on this.
Since Dec 3, 2024.
feature request
nice-to-have
usability
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
job progress reports in a jupyter notebook can take quite some vertical space, e.g.
0:00:00 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': send 'start'
0:00:20 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:00:28 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:00:35 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:00:43 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:00:53 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:01:06 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:01:22 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:01:41 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:02:06 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': queued (progress N/A)
0:02:36 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': running (progress N/A)
0:03:14 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': running (progress N/A)
0:04:01 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': running (progress N/A)
0:05:00 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': running (progress N/A)
0:06:01 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': running (progress N/A)
0:07:02 Job 'vito-j-ca99a93e1d7641d1b4e7a4714d7cfe90': finished (progress N/A)
This progress report is somewhat useful while waiting for the job to finish. But after it has finished, it's usually a waste of vertical space in a notebook.
In a simple text context (e.g. command line execution) there is not much we can do, but in a jupyter notebook context there are tools to create a more dynamic (HTML based) UI instead.
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.