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
When the browser connector fails to connect to a MapD instance, there often is no useful error message in the console. Instead something like this will often show up:
Nothing is visible in the network response either.
It would improve the developer friendliness of this library immensely if we could provide useful error messages.
🆕 If feature request
User story: As an application or data visualization engineer using mapd-core and/or mapd backend rendering, I need to be able to debug mapd-connector when the connection fails.
Specific requirements/functionality:
Mocks (if applicable):
cc @alexbaden@andrewseidl I know there was some related issue about CORS somewhere, maybe you might have some ideas for fixing this as well.
The text was updated successfully, but these errors were encountered:
@nermaljcat is correct, this is an issue with Thrift not handling the .onerror event of the XHR, resulting in the exception blowing up the stack with no info.
🪲 If bug
When the browser connector fails to connect to a MapD instance, there often is no useful error message in the console. Instead something like this will often show up:
Nothing is visible in the network response either.
It would improve the developer friendliness of this library immensely if we could provide useful error messages.
🆕 If feature request
cc @alexbaden @andrewseidl I know there was some related issue about CORS somewhere, maybe you might have some ideas for fixing this as well.
The text was updated successfully, but these errors were encountered: