The AI model provider is experiencing issues (Partially Degraded Service). Fix generation may be delayed or unavailable. View status
Failed
Open on GitHub

perf(router-core): parse the location once in update and build rewrites without arrays view more

MManuel Schiller
89da8066
8422Latest execution

Self-Healing CI

Classification: Flaky task

We classified this E2E failure as flaky rather than a regression from this PR. The failing test (shared widget CSS stays applied when navigating from lazy to static route) has an ~11% historical flakiness rate, belongs to a project untouched by this PR, and its CSS rendering assertion is unrelated to the router-core location-parsing and basepath-rewrite refactor introduced here. We recommend rerunning the task.

An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.

The AI model provider was experiencing issues when this fix was generated.

The failing task tanstack-vue-start-e2e-start-manifest:test:e2e was classified as flaky rather than a code change for three reasons:

  1. Flakiness rate: This task has a measured flakiness rate of ~11.4%, meaning it fails intermittently on identical code — a hallmark of a non-deterministic test.

  2. Unaffected project: The project tanstack-vue-start-e2e-start-manifest is not listed in the touched projects for this PR (root and @tanstack/router-core only). No files in that e2e project were modified.

  3. Unrelated failure domain: The PR is a performance refactor of router-core internals — it optimizes how the location is parsed in update(), simplifies rewriteBasepath to positional arguments, and removes intermediate arrays in invalidate(). The failing test asserts a CSS border color (borderTopColor) is applied after navigating from a lazy route to a static route. CSS module loading and asset injection during client-side navigation are entirely outside the scope of the PR's changes.