query fails silently on parse errors #64
Comments
|
This is because the It might be better to default to the |
maoe
pushed a commit
that referenced
this issue
May 19, 2018
|
I've fixed the issue in the feature/error-handling branch. Could you confirm if case_issue64 is the issue you described and check if it's fixed in this branch? |
maoe
pushed a commit
that referenced
this issue
Sep 16, 2018
maoe
pushed a commit
that referenced
this issue
Mar 26, 2019
maoe
pushed a commit
that referenced
this issue
Jun 17, 2020
maoe
pushed a commit
that referenced
this issue
Jun 17, 2020
Merged
maoe
added a commit
that referenced
this issue
Jun 19, 2020
v1.8.0 This release reworked the QueryResuls type class. There are some breaking changes: * parseResults has been deprecated. QueryResults has now parseMeasurement method. * Decoder has been monomorphized so that it can be used with lens. The original Decoder type has been renamed to SomeDecoder. * QueryParams has now decoder field. * parseResults and parseResultsWith had been using lenientDecoder and it caused some unintuitive behavior (#64, #66). Now they use strictDecoder instead. * parseErrorObject now doesn't fail. It returns the error message of a response. * parseQueryField which has been deprecated is now deleted. * QueryResults instance for ShowSeries was broken. This is fixed. * The constructor of Decoder, parseResultsWith, and parseResultsWithDecoder have been hidden from the top-level module. They're still available from Database.InfluxDB.JSON. See #68 for how to migrate your code from v1.7.x to v1.8.x.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across it when using
(Tagged "time" Int)field. The query was returning no results even though printed and ran by hand was ok. It worked when I changed it toTagged "time" UTCTime. But it broke agains when I set the precision toSecondin query parameters. Now I know that was due to the precision being set torfc3339which returns human readable timestamps. Anyway, the bigger issue here is that parse errors are silent failures.The text was updated successfully, but these errors were encountered: