-
Notifications
You must be signed in to change notification settings - Fork 174
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
feat: merge audit branch #1533
feat: merge audit branch #1533
Conversation
This commit aims at having more flexibility in the dojo storage engine, to automatically use several storage slots segments depending on the packed size. The offset and length fields are not more required for the database to work. The layout is still exposed for the moment.
There were a security issue with the executor, as currently the library_call is not immutable. Hence, a function called by library_call may contains other syscall. For this reason, the executor is removed in favor of deploying the model to get it's name.
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.
some minor feedback from a initial pass
@ThePinion and @neotheprogramist if you have a chance I would appreciate a counter review on the core contracts changes. 🙏 @neotheprogramist you had started hard and great work on indexing, however for the audit it was removed as we should reconsider the model for this in a later phase. Appreciate your comprehension on that mate. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1533 +/- ##
==========================================
+ Coverage 70.06% 70.50% +0.43%
==========================================
Files 236 261 +25
Lines 22531 25300 +2769
==========================================
+ Hits 15786 17837 +2051
- Misses 6745 7463 +718 ☔ View full report in Codecov by Sentry. |
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.
Some comments on the sozo capabilities for backward compatibilities.
Thanks guys for the feedback. 👍
let do_expand: bool = | ||
std::env::var(DOJO_PLUGIN_EXPAND_VAR_ENV).map_or(false, |v| v == "true" || v == "1"); | ||
|
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.
What's the purpose behind this env var? Is there a reason to print out the expanded code ?
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.
Debugging mostly.
While working on dojo-lang
to introduce the array, I found that having the compiler rewritten node expanded was very useful.
The audit branch contains several important changes:
sozo
when the owner of the world deploys it.library_call
syscall.Array<felt252>
in models.Tasks: