You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a path doesn't match, we just return [BricksLLM] route not supported, which makes it slightly tricky to debug API calls made via an SDK, cause the SDK hide the request path from the user.
Maybe would be nice if we also return the request path along with the error, cause sometimes the error is really obvious.
Something like [BricksLLM] "/api/providers/foo/bar" is not a supported route?
The text was updated successfully, but these errors were encountered:
Currently when a path doesn't match, we just return
[BricksLLM] route not supported
, which makes it slightly tricky to debug API calls made via an SDK, cause the SDK hide the request path from the user.Maybe would be nice if we also return the request path along with the error, cause sometimes the error is really obvious.
Something like
[BricksLLM] "/api/providers/foo/bar" is not a supported route
?The text was updated successfully, but these errors were encountered: