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.

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

SigningProcess seems to not effect the ScriptContext in the emulator #373

Closed
Yasuke opened this issue Mar 26, 2022 · 1 comment · Fixed by #384
Closed

SigningProcess seems to not effect the ScriptContext in the emulator #373

Yasuke opened this issue Mar 26, 2022 · 1 comment · Fixed by #384
Labels
bug Something isn't working

Comments

@Yasuke
Copy link
Contributor

Yasuke commented Mar 26, 2022

Summary

When the signing process is set (like in the Spec.MultiSig module of the use-cases-testsuit). It doesn't seem the signatures are added to the transaction.

In the latest plutus, after looking at the Spec module of use-cases it looks like the reason for this is needing to adopt a newer signing API.

Steps to reproduce the behavior

  1. clone plutus-apps
  2. run nix-shell
  3. cd into the plutus-use-cases repo
  4. cabal repl plutus-use-cases-test
  5. ghci> import Test.Tasty
  6. ghci> import Spec.MultiSig
  7. ghci> defaultMain tests
  8. wait for test to fail

Actual Result

2 out of 3 tests failed (0.01s)

is the output from my machine

Expected Result

I expect the tests will pass once the update to the new signing api is complete.

Describe the approach you would take to fix this

No response

System info

OS: NixOS
Plutus: 4127e9cd6e889824d724c30eae55033cb50cbf3e

@Yasuke Yasuke added the bug Something isn't working label Mar 26, 2022
@sjoerdvisscher
Copy link
Contributor

The SigningProcess code looks old to me and I think it should be removed. Do you need it for something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants