Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] - viewState with sortKey not using proper block information #511

Closed
dtfiedler opened this issue Mar 1, 2024 · 2 comments
Closed

[BUG] - viewState with sortKey not using proper block information #511

dtfiedler opened this issue Mar 1, 2024 · 2 comments

Comments

@dtfiedler
Copy link
Contributor

Describe the bug
When providing a sortKey for a read interaction - the global SmartWeave object uses the most recent block height information, instead of the block height specified by the sortKey.

To Reproduce
Run any viewState interaction on a contract that uses a global SmartWeave object in the read interaction execution.

Expected behavior
The block information used for evaluation of read interactions matches the provided sortKey

Desktop (please complete the following information):

  • OS: [e.g. Linux] - Linux
  • Node.js version - 18.17.1
  • warp-contracts SDK version - 1.4.36

Additional context
Related to #504
@dtfiedler
Copy link
Contributor Author

#512

@atticusofsparta atticusofsparta mentioned this issue Mar 1, 2024
Merged
@dtfiedler dtfiedler mentioned this issue Mar 1, 2024
Merged
@asiaziola
Copy link
Contributor

Released in 1.4.37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dtfiedler @asiaziola