@@ -284,11 +284,11 @@ def visit_audit_only_run_stage(
284284 def visit_restatement_stage (
285285 self , stage : stages .RestatementStage , plan : EvaluatablePlan
286286 ) -> None :
287- # Restating intervals on prod plans means that once the data for the intervals being restated has been refreshed
287+ # Restating intervals on prod plans means that once the data for the intervals being restated has been backfilled
288288 # (which happens in the backfill stage) then we need to clear those intervals *from state* across all other environments.
289289 #
290- # This ensures that work done in dev environments can still be promoted to prod
291- # by forcing dev environments to re-run intervals that changed in prod (because after this stage runs they show as missing)
290+ # This ensures that work done in dev environments can still be promoted to prod by forcing dev environments to
291+ # re-run intervals that changed in prod (because after this stage runs they are cleared from state and thus show as missing)
292292 #
293293 # It also means that any new dev environments created while this restatement plan was running also get the
294294 # correct intervals cleared because we look up matching snapshots as at right now and not as at the time the plan
@@ -313,8 +313,8 @@ def visit_restatement_stage(
313313 remove_shared_versions = plan .is_prod ,
314314 )
315315
316- # While the restatements were being processed, did any of the snapshots
317- # being restated get new versions deployed? If they did, they will not reflect the data that just got restated
316+ # While the restatements were being processed, did any of the snapshots being restated get new versions deployed?
317+ # If they did, they will not reflect the data that just got restated, so we need to notify the user
318318 if deployed_env := self .state_sync .get_environment (plan .environment .name ):
319319 promoted_snapshots_by_name = {s .name : s for s in deployed_env .snapshots }
320320
0 commit comments