REST interface for status and DELETE does not consider pipeline name, just the instance id

[tim-shockley]

We have VAS setup with two pipelines available, people-detection and tampering-detection. When I start a pipeline, I can use either pipeline id and VAS returns the status of the instance id. Consider the following output from a bash script that starts the pipeline and then polls the status every 5 seconds.

> bin/run-pipeline.sh tampering
starting http://127.0.0.1:8080/pipelines/object-detection/tampering_detection with params: /home/tshockley/projects/coffee-bay/bin/tampering-detection-params.json
Open VLC at: rtsp://127.0.0.1:8553/tampering-detection-inf
9: {  "avg_fps": 0.0,  "elapsed_time": 5.009296417236328,  "id": 9,  "start_time": 1635292151.0614913,  "state": "QUEUED"}
9: transition from INITIAL to QUEUED
9: {  "avg_fps": 0.0,  "elapsed_time": 10.033835887908936,  "id": 9,  "start_time": 1635292151.0614913,  "state": "QUEUED"}
9: {  "avg_fps": 5.028083418896863,  "avg_pipeline_latency": 1.279581626256307,  "elapsed_time": 4.773182392120361,  "id": 9,  "start_time": 1635292161.3365495,  "state": "RUNNING"}
9: transition from QUEUED to RUNNING
9: {  "avg_fps": 4.901154411447156,  "avg_pipeline_latency": 1.2800498952468236,  "elapsed_time": 9.79360055923462,  "id": 9,  "start_time": 1635292161.3365495,  "state": "RUNNING"}
9: {  "avg_fps": 4.863720792720912,  "avg_pipeline_latency": 1.2772698336177402,  "elapsed_time": 14.803473711013794,  "id": 9,  "start_time": 1635292161.3365495,  "state": "RUNNING"}

But notice I can use either pipeline URL and get the status, and this also is true for DELETE.

> curl "http://127.0.0.1:8080/pipelines/object-detection/people_detection/9/status"
{
  "avg_fps": 4.717405370008668,
  "avg_pipeline_latency": 1.2834804068440977,
  "elapsed_time": 48.75560641288757,
  "id": 9,
  "start_time": 1635292161.3365495,
  "state": "RUNNING"
}

> curl "http://127.0.0.1:8080/pipelines/object-detection/tampering_detection/9/status"
{
  "avg_fps": 4.732447832742834,
  "avg_pipeline_latency": 1.2802955792941588,
  "elapsed_time": 61.49036931991577,
  "id": 9,
  "start_time": 1635292161.3365495,
  "state": "RUNNING"
}

[whbruce]

Thanks for reporting. I was able to replicate. Is this blocking your development?

We'll look into this and get back to you with a timeline for a fix.

[whbruce]

Fixed in v0.7.1.