-
Notifications
You must be signed in to change notification settings - Fork 671
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.
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
at-block function can't take a contract-call even though the called function is a read-only function #2953
Comments
I don't think that's the reason this transaction failed. From my node's log:
Looks like there's a typo in your contract. |
If Clarinet is telling you that this contract is failing because of a read-only violation, then there's a bug in Clarinet. It should have warned you about the typo first. |
Going to go ahead and close this. Please re-open if you get a chance to re-try this. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
I would like to lookup a historical value, like the last-token-id of a SIP 9 NFT
Clarinet check complains with
at-block closures expect read-only statements, but detected a writing operation
Testnet rejects a simple contract as well
https://explorer.stacks.co/txid/0xbec570e026fd9bf43984b768bb891645fe120c176c25070b34015fe939717917?chain=testnet
Describe the solution you'd like
Allow contract-call functions in the
at-block
function if the called function is a read-only function.Maybe even discard changes if it is not a read-only function.
Describe alternatives you've considered
Do it off-chain
Additional context
#1981
#1641
The text was updated successfully, but these errors were encountered: