Introduce BatchRun Object
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 6
Description
Summary
Introduce a BatchRun object to expose status(), wait(), logs(), results(), cancel(). This will also reduce notebook boilerplate when running in a notebook and will simplify interactive workflows.
Blockers/Related work
Note blockers here and in the relationship panel
Definition of Done
Creation of BatchRun object.
Expected amount of work (days)
4
Remove question label once details are complete, change task to bug if bug.
Contributor guide
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
No files, tests, or entry points are named. Start by tracing the existing notebook workflow for running jobs and identify where status, waiting, logs, results, and cancellation are currently handled; done means a BatchRun object exposes all five methods and reduces notebook boilerplate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100