VEuPathDB / VEuPathDB/lib-compute-platform
Exceptions should be caught when setting up the workspaces and cause jobs to...
Open
@Foxcapades is already working on this.
Since Jun 13, 2022.
todo
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 3
Description
What should happen when the creation/setup of a job fails in the platform before the job is executed?
-
Should we assume it's a hiccup and clear out the job with a 500 so they can try resubmitting?
-
Should we just fail the job before it starts?
-
Submitting a job to the DB (we didn't even manage to record the job)
-
Submitting a workspace to S3 (we recorded the job in the DB but S3 operation(s) failed)
-
Submitting a job to the queue (we recorded the job in the DB and created an S3 workspace, but rabbit threw an exception)
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.