Executor version
2.0.0-beta.8 (built from the executor@2.0.0-beta.8 tag with a small server-side patch; the web app is unmodified). The setup route and AccountSelectionPage are unchanged on v2 at ed608b7.
How do you run Executor?
Self-host (Docker)
Operating system
Linux (Chrome)
What happened
Opening /org/<org>/apps/<app>/setup, with or without ?profile=, never leaves the page. The main area stays empty, the tab stops responding, and eventually Chrome shows "Aw, Snap!" (SIGILL). It happens for every app we tried; every other dashboard page works.
AccountSelectionPage (apps/hosted/web/src/implementation/pages/account-selection.tsx) renders <Navigate params={{…}} search={{…}} replace /> with new objects on every render. TanStack Router's Navigate (1.170.41) calls navigate(props) in a layout effect whenever props changes. The navigation re-renders the setup route before it commits, which creates new props and starts the next navigation, so it never completes. Pausing the frozen tab shows Navigate's effect → router.navigate → commitLocation → load, over and over.
What you expected
One redirect to /org/<org>/apps/<app>?view=accounts, which works when opened directly.
Steps to reproduce
- Sign in to the dashboard.
- Open
https://<host>/org/<org>/apps/<any app id>/setup.
- The tab stops responding within a few seconds.
Redirecting in the route's beforeLoad (throw redirect(...)) instead of rendering <Navigate> would likely avoid it.
Diagnostics / logs
Nothing on the server; the loop runs in the browser.
Executor version
2.0.0-beta.8 (built from the
executor@2.0.0-beta.8tag with a small server-side patch; the web app is unmodified). The setup route andAccountSelectionPageare unchanged onv2at ed608b7.How do you run Executor?
Self-host (Docker)
Operating system
Linux (Chrome)
What happened
Opening
/org/<org>/apps/<app>/setup, with or without?profile=, never leaves the page. The main area stays empty, the tab stops responding, and eventually Chrome shows "Aw, Snap!" (SIGILL). It happens for every app we tried; every other dashboard page works.AccountSelectionPage(apps/hosted/web/src/implementation/pages/account-selection.tsx) renders<Navigate params={{…}} search={{…}} replace />with new objects on every render. TanStack Router'sNavigate(1.170.41) callsnavigate(props)in a layout effect wheneverpropschanges. The navigation re-renders the setup route before it commits, which creates new props and starts the next navigation, so it never completes. Pausing the frozen tab showsNavigate's effect →router.navigate→commitLocation→load, over and over.What you expected
One redirect to
/org/<org>/apps/<app>?view=accounts, which works when opened directly.Steps to reproduce
https://<host>/org/<org>/apps/<any app id>/setup.Redirecting in the route's
beforeLoad(throw redirect(...)) instead of rendering<Navigate>would likely avoid it.Diagnostics / logs
Nothing on the server; the loop runs in the browser.