Closed InterferencePattern closed 6 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.
This is not a bug per se, but falls into the category of improvements. The current setup of the Rest API's RestClientObject has a method called
request
that does not return an error in the case of a connection error. The only instance where it handles the error is SSLError. However, there are a number of additional connection errors that should throw errors instead of providing empty results (which can be misinterpreted by the end user.) Additional errors which can be handled are listed here: https://urllib3.readthedocs.io/en/stable/reference/urllib3.exceptions.html#urllib3.exceptions.HTTPErrorThis became particularly evident when I tried to follow these instructions to access Kubeflow Pipelines from outside my AWS cluster. In that case, running the following failed to return an error, even though it did not receive a result via GET from the server:
Environment
Steps to reproduce
From off-server on AWS:
Expected result
Either a list of experiments on the server, or an error message stating the reason it failed to connect.
Materials and Reference
Impacted by this bug? Give it a 👍.