We are running the simulation of an upgrade proposal and are getting weird results in the Storage section. It looks like there are two storage slots that are getting updated, then getting reverted at the same time. I executed an upgrade in forking mode and the implementation slot is updated successfully so there must be an issue with reporting the reverts in the simulation.
This looks related to the rollback test performed by the proxy during the upgrade, though it's not clear to me how upgradeTo ends up performing the rollback check. For reference, the proxy is here. Even in this case, shouldn't we have a 5th slot update that updates to the new implementation in the end of the simulation?
Environment
Details