Closed jbrzusto closed 6 years ago
Happens with any jobID that isn't valid.
This is due to my having allowed for the ID of a non-top-level job to be supplied.
list_jobs()
looks up the stump, but fails to deal correctly with an invalid jobID,
which in turn leads to a collapse of the id-filtering portion of the DB query, and
that means we get back all jobs.
typically causing a browser to fail on a huge memory allocation
e.g. this URL does it:
https://sgdata.motus.org/status?jobID=0