feat: auto-set block timestamp for historical queries (#15448) #440
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
p0mvn
added a commit
that referenced
this pull request
May 8, 2023
p0mvn
added a commit
that referenced
this pull request
May 8, 2023
…(backport #440) (#441) * feat: auto-set block timestamp for historical queries (cosmos#15448) (backport #440) * updates * updates * updates --------- Co-authored-by: Roman <roman@osmosis.team>
p0mvn
added a commit
that referenced
this pull request
May 9, 2023
p0mvn
added a commit
that referenced
this pull request
May 9, 2023
…(backport #440) (#442) * feat: auto-set block timestamp for historical queries (cosmos#15448) (backport #440) * go mod tidy --------- Co-authored-by: Roman <roman@osmosis.team>
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.
Closes: #XXX
Backport: cosmos#15448
What is the purpose of the change
This was breaking historical TWAP queries since the block time would always be set to the latest block time, and not the historical block time.
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note
Unreleasedsection inCHANGELOG.md? no