Run forge test to see the issue. test_storage has an assert at the bottom that shouldn't be failing. What's weirder is that simply reading the bridges length before forking in the test fixes the issue. My guess is there is some edge case bug with storage persistence across forks with this setup.
-
Notifications
You must be signed in to change notification settings - Fork 0
hexonaut/fork-storage-issue
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
Weird issue with forks losing some state.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published