-
-
Notifications
You must be signed in to change notification settings - Fork 76
Proposal Procedures dropped from script context during evaluation #438
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
Comments
Thanks @nielstron for reporting this issue. The deepcopy seems to be the main reason why the proposal was included in the script context. After adding deepcopy, the values provided in the proposal showed up in the message of unroll script. Also, notice how the reward account is added differently from your example above. This is required in order for the script context to be successfully unrolled. I added an integration test to make sure it actually happened here.
For the context, here is one of the cbors passed to Ogmios for evaluation:
and it certainly contains
|
Is there any remaining issue with the fix, or is it good to close this now? |
Describe the bug
I am trying to extract the script context from a script invocation in PlutusV3 including Proposal Procedures. However, using the script I wrote for this purpose, the log indicates that the proposal procedure is not included correctly in the script context during evaluation. Closer investigation revealed that deepcopy on the NonEmptyOrderedSet of proposal procedures appears to return an empty set.
I was able to resolve this by adding the following method to NonEmptyOrderedSet (however am now faced with "invalid reward address header"):
To Reproduce
The following script always tries to unroll the script context parameter, raising an error in ogmios that dumps the script context
script.cbor
It has following address:
Logs
Expected behavior
Should include the proposal procedures in the script context
Environment and software version (please complete the following information):
The text was updated successfully, but these errors were encountered: