Bug #8628
closed
- Detected in build set to svn
- Tracker changed from Feature to Bug
- Priority changed from High to Urgent
- Target version set to 3.0
Moreover, it can corrupt the database. For instance, when I tried to store a job with a long name (after editing existing job files and the job name), Bridge outputted an unknown error. After reducing the job name there was jobs.models.JobHistory.MultipleObjectsReturned .
- Status changed from New to Feedback
Can't reproduce the bug in bridge-3.0.
- Due date set to 07/10/2019
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
There are warnings about big job length, so the bug is not relevant now (bridge-3.0).
- Status changed from Resolved to Closed
- Subject changed from Properly restrict job name lenght to Properly restrict job name length
Also available in: Atom
PDF