Open kaspar030 opened 2 weeks ago
I can confirm that pinning hax_reference
to d10f891a19f96bcafa9e31b1d78763e4f3cf30b4 makes our CI work again, we'll be temporary doing that.
Hi, thanks for the report!
I will try to look at before the end of the day, I suspect that it is something easy to fix. We changed a convention and our F* core library may be not entirely updated yet, hence the problem you have here.
This issue is related to https://github.com/hacspec/hax/issues/719. One patch we merged for solving #719 yielded this issue, but was not fixing entirely #719. Thus, fixing this issue now would just make it re-appear differently when #719 is fixed. I'm thus waiting for #719 to be fixed before fixing this one.
Hi,
our CI just broke on unchanged code:
We're using the hax action from "master", so I'm assuming some of the just merged changes here are the cause. Let me know if I can provide more info!