Closed sebastian closed 4 years ago
Looks to me like it might due to a difference in api version on the air
you are using compared to what we test against?
There's an issue parsing the reply from the /datasources
endpoint. Specifically, the isolating
specifier: it expects a json boolean value but is getting a string instead.
As to why this doesn't show in Sentry... I have no idea, I'll look into it.
Ok, I'll fix this and will log a separate issue for the missing sentry event.
Should the explorer assume a field is Isolating until proven otherwise? Or the reverse?
Isolating until proven otherwise
It can take any of the following values (see here and here for more details):
- true
- false
- "failed"
- "pending"
- "unknown_column"
Would it make sense to modify this, so that all values will have the same type?
This will require significant changes in cloak
, so this will not happen.
Internally it's treated as:
true
or false
I think that is correct as such. Arguably bunching all these different outcomes into a single value without indicating whether it is a success or error condition is awkward.
I am trying to access the latest API endpoint. All requests fail with:
This happens for every single request, and results in a 500 exception. Why isn't this reported to sentry?