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

illegal::validator_arity - Please remove the 4294967295 extra arguments #1013

Closed
1 of 4 tasks
rhystmorgan opened this issue Sep 5, 2024 · 0 comments
Closed
1 of 4 tasks

Comments

@rhystmorgan
Copy link

What Git revision are you using?

aiken v1.1.0+be31a7c

What operating system are you using, and which version?

  • Linux / Ubuntu
  • Linux / Other
  • macOS
  • Windows

Describe what the problem is?

When I was updating validators to Pv3 I came up against this error:

jumpingTheGunWhenMigrating - Copy
error

Obviously there aren't that many arguments

I hadn't updated the .toml file so it was still using stdlib 1.9.0
I had not finished the migration to V3 syntax, so I still had ScriptContext as the function argument

The only reason I came up against this is because I saved, switched to terminal, ran aiken check out of habit

As soon as I fixed the issues in my code, to Pv3, and updated .toml the error went away

What should be the expected behavior?

I'm unsure what caused it as this is invalid syntax for both versions.

It could be:

  • Named validator not compatible with Pv2
  • no function declaration for mint
  • ScriptContext not compatible with Pv3 syntax

there are several problems with the code in the image attached ( I know ) I have just added it here because Ktorz said it is good to track these small things

I am happy to provide more info if needed

@github-project-automation github-project-automation bot moved this to 🪣 Backlog in Project Tracking Sep 5, 2024
@KtorZ KtorZ closed this as completed in 19e30b1 Sep 6, 2024
@github-project-automation github-project-automation bot moved this from 🪣 Backlog to ✅ In Next Release in Project Tracking Sep 6, 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