Skip to content

perf(nimbus): compute rollout review errors once per render - #17152

Merged
jaredlockhart merged 6 commits into
mainfrom
17151
Sep 16, 2026
Merged

jaredlockhart merged 6 commits into
mainfrom
17151

Conversation

@jaredlockhart

@jaredlockhart jaredlockhart commented Sep 4, 2026 •

Copy link
Copy Markdown
Collaborator

Because

  • Rendering a rollout page runs eleven full rollout review validation passes.
  • The sidebar reads the review error state ten times and the setup progress computes it again.

This commit

  • Computes the rollout review errors once in the shared setup-progress context and has the sidebar read that, rather than each template reference recomputing them.
  • Adds the setup-progress context to the archive toggle view, which also renders the sidebar.

Fixes #17151

@jaredlockhart
jaredlockhart force-pushed the 17151 branch 2 times, most recently from cb907f1 to d78937a Compare September 4, 2026 19:31
@jaredlockhart jaredlockhart changed the title perf(nimbus): cache rollout review errors perf(nimbus): compute rollout review errors once per render Sep 4, 2026
Because

* Rendering a rollout page runs eleven full rollout review validation passes.
* The sidebar reads the review error state ten times and the setup progress computes it again.

This commit

* Computes the rollout review errors once in the shared setup-progress context and has the sidebar read that, rather than each template reference recomputing them.
* Adds the setup-progress context to the archive toggle view, which also renders the sidebar.

Fixes #17151

@RJAK11 RJAK11 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested the changes locally and everything seemed to behave correctly and the changes all make sense to me! 🎉

Because

* The phase factory defaults every phase to start today, so two phases
  always overlap and fail the rollout review sequence check.
* That left the review-valid case of the advance-phase test asserting an
  enabled button on a rollout that still had review errors.

This commit

* Pins explicit contiguous start and end dates on both phases so the
  risk_brand value is the only thing the two cases differ on.
@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 15, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 15, 2026
@jaredlockhart
jaredlockhart added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit 3d99f22 Sep 16, 2026
32 checks passed
@jaredlockhart
jaredlockhart deleted the 17151 branch September 16, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rollout sidebar runs eleven review validation passes per render

2 participants