The first plugin instance sometimes fails to be saved correctly
- Dominant language
- Go Template
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/FNNDSC/ChRIS_ultron_backEnd/blob/9ac090810bdff11ce0a6ca99961c94afd62f9cf6/chris_backend/plugininstances/services/manager.py#L183-L189
The job runs properly, and in the log we see "Successfully submitted job" however the plugin status remains `scheduled` instead of being changed to `started`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with plugininstances/services/manager.py at lines 183-189 and compare the successful job submission path with the persisted plugin status. Reproduce or trace the first plugin instance case using the log message "Successfully submitted job"; done means the status changes from `scheduled` to `started` reliably after submission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100