-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: setup caracal #413
chore: setup caracal #413
Conversation
Marked as ready to test CI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, it runs now! The reporting is a little meh, since we have to check the output every time right?
Should we be addressing the findings? There's one high impact:
felt252-overflow Impact: High Confidence: Medium
The function aura::utils::types::StoreYangRedistribution::read uses the felt252 operation felt252_sub([62], [63]) -> ([64]), which is not overflow safe
Yes, and it looks like there can be quite a number of false positives, although there is no other alternative at the moment.
Honestly, I am not sure what to make of this finding, whether it is a false positive and whether it is within our means to fix it. My best guess is that it relates to the corelib's implementation of the |
btw, this depends on #399. |
Seems like it, but then there's no |
Weird error. |
There were some changes to Scarb in the nightly release yesterday that broke this CI. I have filed a PR but it will need to wait for Caracal to be bumped to the next Scarb release after v0.7.0 (unless we build Caracal from source). |
24b6667
to
fc56bf8
Compare
caracal 0.2.2 was just released a couple of hours 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolves #389.