-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Ambiguous errors #6
Comments
+1 |
1 similar comment
+1 |
@brokentone Could you provide more details? I haven't seen this before—the URI is always populated. If you could let me know which route you were trying to hit, I can try to reproduce. |
Yeah, definitely any other information to go on here would be a huge help. There was a change made last October to include the request path on the SDK Error objects. I'm perfectly happy to modify or extend this output though if I can do anything to make the errors easier to understand. Given those stack traces, the only way that particular outcome could manifest would be if no URL value existed for that |
Is there any way to log anything better here?
The text was updated successfully, but these errors were encountered: