From 968b482d7a51edc16c6291fbf817781285f54f35 Mon Sep 17 00:00:00 2001 From: Aayush Date: Tue, 27 Feb 2024 21:07:44 -0500 Subject: [PATCH] do NOT update the cache when running the real migration --- chain/stmgr/forks.go | 4 ---- 1 file changed, 4 deletions(-) diff --git a/chain/stmgr/forks.go b/chain/stmgr/forks.go index 9dd66ee8bcc..93f53c63ff0 100644 --- a/chain/stmgr/forks.go +++ b/chain/stmgr/forks.go @@ -203,10 +203,6 @@ func (sm *StateManager) HandleStateForks(ctx context.Context, root cid.Cid, heig log.Errorw("FAILED migration", "height", height, "from", root, "error", err) return cid.Undef, err } - // Yes, we update the cache, even for the final upgrade epoch. Why? Reverts. This - // can save us a _lot_ of time because very few actors will have changed if we - // do a small revert then need to re-run the migration. - u.cache.Update(tmpCache) log.Warnw("COMPLETED migration", "height", height, "from", root,