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

uplc - misleading error message returned by eval_phase_two #974

Closed
2 tasks done
HinsonSIDAN opened this issue Jul 11, 2024 · 0 comments
Closed
2 tasks done

uplc - misleading error message returned by eval_phase_two #974

HinsonSIDAN opened this issue Jul 11, 2024 · 0 comments

Comments

@HinsonSIDAN
Copy link

HinsonSIDAN commented Jul 11, 2024

What Git revision are you using?

git version 2.39.3 (Apple Git-146)

What operating system are you using, and which version?

  • macOS
  • Windows

Describe what the problem is?

When conducting evaluation of a simple transaction with 2 inputs:

  • One input from a pub key address, without providing the utxos: &[ResolvedInput] information
  • One script input with input information providing thru utxos: &[ResolvedInput]

It would return error:
msg: "Error occurred during evaluation: Redeemer (Spend, 1): Resolved Input not found.". It is misleading for dev to seek for error in providing utxos for the second input (script input), but the issue actually comes from missing first input (the pub key input)

What should be the expected behavior?

Should return correct error message, indicating it is the pub key input missing (for example, without saying it is the Redeemer (Spend) issue, since it naturally route dev to look at the script input provided.

It may sounds trivial, but spent me 2 hours to figure it out, hope fixing this issue can save other devs unnecessary debugging time!

@HinsonSIDAN HinsonSIDAN changed the title Misleading error message returned by eval_phase_two uplc - misleading error message returned by eval_phase_two Jul 11, 2024
@KtorZ KtorZ closed this as completed in b28d4a6 Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ In Next Release
Development

No branches or pull requests

1 participant