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
Hi, I've been using this library for some time and I'm quite loving it for writing some tick data into influxDB. I recently ran into an issue where writes were failing cause of data type mis matches (trying to write integer to a float field).
The logs were returning response of 0, which should be okay, but then I dug deeper and saw it's ALWAYS returning 0.
Is there a way to change the log WriteEntry to actually return an error response instead of response always being set to 0?
The text was updated successfully, but these errors were encountered:
Apparently there is no direct way because for whatever reason I decided to not set the result of the write request into the log entry 🤦
The only somewhat usable way before having a more usable base logging in place (just added the result contents to the unreleased main branch) would be to hook into the writer:
Hi, I've been using this library for some time and I'm quite loving it for writing some tick data into influxDB. I recently ran into an issue where writes were failing cause of data type mis matches (trying to write integer to a float field).
The logs were returning response of 0, which should be okay, but then I dug deeper and saw it's ALWAYS returning 0.
Is there a way to change the log
WriteEntry
to actually return an error response instead of response always being set to0
?The text was updated successfully, but these errors were encountered: