Opened 16 years ago
Closed 16 years ago
#1082 closed enhancement (fixed)
Make it possible to re-enter parameters for a failed job
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 2.8 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
This is actually quite difficult. The main problem is that the configuration of a job can be highly dependent on the context it was started in. The context information is not saved to the database and what is in memory may have changed since the user has been clicking around since the job was created.
Most plug-ins are probably not affected by this since they just ask for simple parameter values (string, booleans, numbers, etc.). Plug-ins that use the current context for getting information (particularly export plug-ins) may not work as expected when restarted.
The minimal requirement for being able to re-configure a job is that we know the context it was started in, eg. [SAMPLE, LIST], [EXPERIMENT, ITEM], etc... The first approach will be to store this information in the job table, and then try to fix problematic plug-ins as we find them.
Change History (4)
comment:1 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
comment:3 by , 16 years ago
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I have not been able to find any plug-ins that have problems with this. But I have only tested a few of them. Sometimes the hard part is to deliberately generate a failure. So, I am closing this ticket now. Plug-in specific problems should be reported as new tickets.
(In [4378]) References #1064, #1082, #1050, #1024, #967
Updated UML diagrams as a result of new db columns added by the referenced tickets.