Open dpsutton opened 4 years ago
@dpsutton Looks like it's definitely friends with #12586 and possibly #12600
Yeah it looks like those are all instances of this fundamental bug: we intersperse results JSON with error JSON and its not a coherent mix.
While trying to repro https://github.com/metabase/metabase/issues/12586, which pointed out that we could use this issue to repro that one too, I found that I couldn't reproduce the error anymore.
I'm using master
@ e55e7f78c74526472e8b5aa4996a45e9157cb445
Though the timestamp display is definitely weird, it won't crash the question like when it was reported
Describe the bug Error in https://github.com/metabase/metabase/issues/12761 . Postgres allows for "infinity" datetimetz values which we currently don't handle. Our query processor throws an error when previewing this table and this stacktrace/error is interspersed in the streaming response.
Note the exception map is well formed but the original structure of data and rows is now just abandoned resulting in an invalid JSON payload
Can repro the query (but not with interspersed error/results) with
Logs
Note the underlying bug here is being worked on in the linked ticket. This bug report is about error handling in the streaming query response NOT the instant error here.
To Reproduce If the infinity timestamptz bug is not fixed or you can back out that patch,
sync your database then click on the
demonstrate
table and you should get this malformed JSON response.Expected behavior I'm honestly not sure. A couple possibilities:
Severity The error handling seems to be decent here. The UI just shows
Which is a decent response to something going wrong. Its just a bit off that we are generating invalid JSON.