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

Update bindings #1011

Closed
wants to merge 1 commit into from
Closed

Update bindings #1011

wants to merge 1 commit into from

Conversation

L-as
Copy link

@L-as L-as commented Jun 30, 2023

Notably includes o1-labs/o1js-bindings#63

@mitschabaude
Copy link
Collaborator

mitschabaude commented Jun 30, 2023

looks like you have to merge main in the bindings PR

@L-as
Copy link
Author

L-as commented Jul 1, 2023

Do I need to declare the function in some TS file?

@mitschabaude
Copy link
Collaborator

Do I need to declare the function in some TS file?

No that's not it, what CI shows is a runtime error

@mitschabaude
Copy link
Collaborator

mitschabaude commented Jul 1, 2023

You need to push updated artifacts created by npm run bindings

@mitschabaude
Copy link
Collaborator

Do you still want to land this @L-as? The tests don't work, I'm pretty sure that's just because you didn't check our the bindings submodule at the latest commit of the bindings PR

@L-as
Copy link
Author

L-as commented Jul 27, 2023

@mitschabaude Sorry for the very late response, but I don't understand why it fails honestly, neither do I understand your hypothesis, because I merely advanced the commit once to include the new functions. I looked at the error when I first pushed the commit and mentally made a note to look at it again, and at that time I assumed it was because I was missing something somewhere to properly export the function, though it works locally (under different circumstances). I wouldn't be so sure it's not buggy but if you believe it isn't then 🤷 .

@mitschabaude
Copy link
Collaborator

mitschabaude commented Jul 31, 2023

@mitschabaude Sorry for the very late response, but I don't understand why it fails honestly, neither do I understand your hypothesis

@L-as on this PR, if you click on "Files changed", then you see that in the bindings submodule, nothing in the /compiled folder changed. This means you don't update the compiled bindings. But snarkyjs CI needs those, therefore the tests here fail.

So, to land this PR, do the following:

# you are in /snarkyjs
# build updated bindings
npm run bindings

# push those to the bindings PR
cd src/bindings
git add compiled
git add MINA_COMMIT
git commit -m "update bindings"
git push

# update snarkyjs PR
cd ../..
git add src/bindings
git commit -m "bindings"
git push

@L-as
Copy link
Author

L-as commented Aug 13, 2023

I will get back to this

@Trivo25
Copy link
Member

Trivo25 commented Jul 11, 2024

stale

@Trivo25 Trivo25 closed this Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants