Skip to content

Commit

Permalink
do NOT update the cache when running the real migration
Browse files Browse the repository at this point in the history
  • Loading branch information
arajasek authored and rjan90 committed Mar 22, 2024
1 parent 5924674 commit 968b482
Showing 1 changed file with 0 additions and 4 deletions.
4 changes: 0 additions & 4 deletions chain/stmgr/forks.go
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down

0 comments on commit 968b482

Please sign in to comment.