JSONParse error on Postgres db error about looker-sdk-ruby

[jbandhauer]

Not an SDK bug. This is a known query API issue.

Note that for some query errors that occur after the results are already streaming we do intentionally embed errors into a 'success' response. That happens because if the error can't be detected until some of the rows are already streamed then there isn't a lot of choice; there is no good way to signal an error at that stage because HTTP requires setting the result code at the start of the response. So, if the error is detected after a bunch of rows have already been streamed then we just stick the error into the result stream and close the connection.

But, in this case we should be signalling the error better. This is a side effect of some legacy looker code on how it returns query errors to the browser.

[cworsley4]

Thanks for the info @jbandhauer.