-
Notifications
You must be signed in to change notification settings - Fork 18
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
Can't leak crate-private traits error in libcrux-ml-kem #189
Comments
@Nadrieril I want to change the priority of this issue (make it P1) but it doesn't appear in the dashboard. Any idea where the issue comes from? (I had to add the issue by hand) |
Yeah it's a known limitation. GitHub project has an option to auto-import issues from one repo but only one. I chose aeneas a bit arbitrarily; this means we need to add charon issues to the project by hand. If we paid for a GitHub plan we'd have the option to auto-import from more repos. There might also be a way to use GitHub Actions to automate this, I'll have to look into it. |
@msprotz Can you try with latest charon main? |
Yup I just need to wrap up my trait work first then will attempt upgrading tool versions. Expect a few days' delay. |
Actually I just saw this again. Will try to send a repro soon. |
Has this happened again since? |
I think the code got rewritten and I don't remember which set of revisions last triggered it. I'm ok with closing, and we'll reopen it if it resurfaces. Thanks. |
Here are the revisions I'm working off of:
If I try to extract libcrux-ml-kem, I get:
The text was updated successfully, but these errors were encountered: