NOISSUE - Fix Timescale Reader query #2120
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Musilah
reviewed
Mar 19, 2024
It works okay on my end. Could you show the errors that are coming about |
arvindh123
approved these changes
Mar 21, 2024
arvindh123
approved these changes
Mar 21, 2024
I had mistakenly copied. It runs fine. |
Musilah
approved these changes
Mar 21, 2024
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
dborovcanin
force-pushed
the
noissue-fixreader
branch
from
7447185 to
7f5e951
Compare
dborovcanin
approved these changes
Mar 26, 2024
JeffMboya
pushed a commit
to JeffMboya/supermq
that referenced
this pull request
Apr 3, 2024
Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a big fix
What does this do?
This pr fixes the query for the timescale reader to sync with the current update of saving to nanoseconds.
Which issue(s) does this PR fix/relate to?
NOISSUE
Have you included tests for your changes?
NO
Did you document any new/modified feature?
NO
Notes