We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
By coincidence (docker-compose didn't use the latest engine image where listCatalogs got implemented), I came across an unwanted behavior if a page of the engine is not reachable. In this case, it was the apiUrl of listCatalogs : https://github.com/clouditor/ui-next/blob/cb3fdee539b9c45a11d9d0ec83fde80b2adac677/src/lib/orchestrator.ts#L241-L255
listCatalogs
apiUrl
The browser tries continuously to refresh the page while also doing auth every time. I played a round a little bit and a simple
.catch((message) => { return null})
would do the trick. Maybe wo could even change the throwError function to consider 404 Not Found not as an error, but I think that doesn't make sense.
throwError
404 Not Found
What do you think @oxisto
The text was updated successfully, but these errors were encountered:
No branches or pull requests
By coincidence (docker-compose didn't use the latest engine image where
listCatalogs
got implemented), I came across an unwanted behavior if a page of the engine is not reachable. In this case, it was theapiUrl
oflistCatalogs
:https://github.com/clouditor/ui-next/blob/cb3fdee539b9c45a11d9d0ec83fde80b2adac677/src/lib/orchestrator.ts#L241-L255
The browser tries continuously to refresh the page while also doing auth every time. I played a round a little bit and a simple
would do the trick.
Maybe wo could even change the
throwError
function to consider404 Not Found
not as an error, but I think that doesn't make sense.What do you think @oxisto
The text was updated successfully, but these errors were encountered: