When running the frontend, viewing an unpublished dataset by going to the url "localhost:2503/dustmop/my_dataset" produces a red alert box with "error 404: " despite the dataset existing, and properly rendering in the UI. This is caused by the dataset not being found on the registry, causing an action to fire with type "REGISTRY_DATASET_FAILURE" and the above error message. Multiple fixes are needed:
The registry returns an error status 500 with message "error 404: ". The status should be 404.
There's no test case in qri/api/registry_test for a GET.
The frontend should ignore registry "not found" errors, if the dataset can be retrieved locally.
When running the frontend, viewing an unpublished dataset by going to the url "localhost:2503/dustmop/my_dataset" produces a red alert box with "error 404: " despite the dataset existing, and properly rendering in the UI. This is caused by the dataset not being found on the registry, causing an action to fire with type "REGISTRY_DATASET_FAILURE" and the above error message. Multiple fixes are needed: