-
Notifications
You must be signed in to change notification settings - Fork 91
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
check that diamond storage is untouched after each pr #636
check that diamond storage is untouched after each pr #636
Comments
/start |
Skipping |
Hello @zgorizzo69 ,
I am thinking of checking the diamond storage before creating a PR and after |
Do you have any updates @PhantomCracker? If you would like to release the bounty back to the DevPool, please comment |
This is work in progress |
Perhaps @rndquu might be able to help with this question. |
I did it in another way so we are good now, thank you! |
I just realized that a week to create a single I will need to lower the time estimate to a day if the current assignee is unable to complete. |
I will try to finish as fast as possible. |
Need to test a few more things here and I will come back with updated PR |
name: Check Diamond Storage |
Available commands
|
this issue is already taken by the other bounty hunter, pls find an issue with no assignee |
I think that a fully GitHub Action implementation makes a lot more sense actually vs what we have going on in the associated pull request. I'm just unsure if it makes sense to throw an error on CI if changes happen. I don't think the pull request reviewers should be expected to manually check the CI logs every time before merging. |
Hei @pavlovcik, |
It might be best to post a comment in the pull request so that we don't need to dig through the CI logs, similar to what we do already for the deployments. |
This issue is really tricky We have a diamond contract which includes all the facets. Each facet has a struct (example) which is used as a storage in a unique slot (example). So on each PR we should check that:
So there should be a script that fetches storage layouts from all of the facets (perhaps via forge inspect) and compares the structure in the PR with the structure in the |
Releasing the bounty back to dev pool because the allocated duration already ended! |
/start |
gitcoindev/foundry-storage-check fork Use foundry-storage-check fork with diamond storage support. Resolves: #636
…nges As requested during pr review. Resolves: #636
…hanges As requested during pr review. Resolves: #636
As discussed during PR review. Resolves: #636
…rary search Treat each input as a NAME, use basename -a option instead of -s. Testing detected that using -s option lost LibAccessControl library. Resolves: #636
As discussed during PR review. Resolves: #636
Use the same solution that was implemented for core contracts. Resolves: #636
Thanks @rndquu @molecula451 @pavlovcik this was a significant effort not only for me but also for you, checking, testing and commenting took a lot of time. Now it seems that the bot was overwhelmed by all of this, seeing this number of comments and did not trigger any comment nor triggered any incentives . I hope we can get this fixed and make the bot generate all incentives correctly. |
We are texting in the group chat about it now t.me/ubiquitydao Please know that this is a priority for us to address this We are scrambling for a fix now Thanks for your contributions and your patience. |
Permit generation skipped because wallet private key is not set If you enjoy the DevPool experience, please follow Ubiquity on GitHub and star this repo to show your support. It helps a lot! |
Task Assignee Reward[ CLAIM 800 WXDAI ]
If you've enjoyed your experience in the DevPool, we'd appreciate your support. Follow Ubiquity on GitHub and star this repo. Your endorsement means the world to us and helps us grow!We are excited to announce that the DevPool and UbiquiBot are now available to partners! Our ideal collaborators are globally distributed crypto-native organizations, who actively work on open source on GitHub, and excel in research & development. If you can introduce us to the repository maintainers in these types of companies, we have a special bonus in store for you! |
Task Creator Rewardzgorizzo69: [ CLAIM 5.7 WXDAI ] |
also looks like it missed lot of the conversational rewars, looks like couldn't handle many commenting?. Would be nice see it re-triggered @rndquu |
Congratulations @gitcoindev for finishing this issue! Pretty hard one :) |
We will re-trigger when the bot is switched back to the |
@rndquu i think we should try to re-trigger conversational rewards here, i think the bot is reacting to those on your calls, there were helpful comment here to reach the goal (which after a couple of days) the PR was nice |
I don't really want to re-trigger anything because rewards generation is kind of unpredicted right now. Let's wait for a stable bot's release. |
best would be to add a gh action to make sure that we haven't messed with the diamond storage
The text was updated successfully, but these errors were encountered: