Investigate using strong memoize for current_migration
We should look into whether using strong memoize within current_migration
method in migration_worker.rb is possible
The following discussion from !70429 (merged) should be addressed:
-
@cwiesner started a discussion: suggestion (non-blocking): What do you think about using strong memoize within
current_migration
? This line wouldn't be needed andcurrent_migration
could be used/called everywhere instead.