fix: shared mutable private getter fixes#6652
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Proof generationEach column represents the number of threads used in proof generation.
L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.
Stats on running time collected for app circuits
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method | Metric | | |
91361db to
8cbd13d
Compare
7ce1f9f to
9e276ec
Compare
…ion (#6653) Mitigates failing state vars test
9e276ec to
4ce1f0e
Compare
…6654) Adding another state vars test that fails
LHerskind
left a comment
There was a problem hiding this comment.
Unsure what the boxes issue is, but I think we are good to 🚢

When I was making some changes to the SharedMutablePrivateGetter, I ran into some issues with it.
The first was that the context variable was not being correctly updated / propogated due to not passing it as a mutable reference. The second was that the SharedMutablePrivateGetter was reading the delay of slot of its own address, and not reading the address of the specific other contract to read from. The value was reading correctly but the delay was not. I added two tests, one as a basic one to test max_block_number propogation, and the other to test changing delays in SharedMutable, and seeing whether the SharedMutablePrivateGetter would accurately reflect those changes.