bug: DELETE
ing the current run only marks it as not current without deleting it
#10909
Labels
bug
robot server
Affects the `robot-server` project
robot-svcs
Falls under the purview of the Robot Services squad (formerly CPX, Core Platform Experience).
Overview
DELETE
ing a run over HTTP seems to only actually delete it if it isn't the current run. If it is the current run, theDELETE
merely marks it as not current, without actually deleting it.Steps to reproduce
POST
a run over HTTP withPOST /runs {"data": {}}
.GET
the run withGET /runs/{id}
and see that it's"current": true
.DELETE
the run withDELETE /runs/{id}
. You'll get an empty{}
response back with an HTTP 200 code.GET
the run again. It will still be there, but now it will be"current": false
.DELETE
the run a second time. You'll get the same empty{}
response with an HTTP 200 code.GET
the run again. Now it will be a 404 error, as expected.The text was updated successfully, but these errors were encountered: