-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deep links to workflows, and reload, no longer work #2103
Comments
I am so far unable to reproduce this. I tried both with webpack and with the server on both master and the release branch. Could you provide more details? Browser? How are you running the server? Screen cap? |
I'll take a quick look. |
My ui is behind a reverse proxy (technically two, an oauth2 proxy and a traefik instance), but I really don't think that is the issue. If you open the debugger and browse around, the ui never actually loads /workflows/[namespace]/[ID], it only loads /workflows and then calls out to /api/v1/workflows/[namespace]/[ID]. When you hit reload on a workload view , the browser actually tries to visit that URL, and then I get the 404. |
Browser is |
That shows the flow of requests that I see. The xhr for the /api/v1/.... work just fine, but the initial browsing two the workflows view never uses /workflows/argo/... . |
Aha! I found the issue here (thanks to your screen cap). Seems like it is the same issue that came up in Argo CD: argoproj/argo-cd#2114. I.e., WebPack doesn't like when it has to route URLs with periods in them. Luckily, this has a very simple fix: argoproj/argo-cd#2162 Thanks for providing such good debugging information! Will submit a PR shortly. |
What happened:
What you expected to happen:
I can no longer directly link from another ui to the workflow URL. Also, if I am viewing a workflow, and ctrl-r reload, it doesn't work. Both workflows get a 404
How to reproduce it (as minimally and precisely as possible):
visit /workflows
click on a workflow
hit ctlr-r
similarly, copy the URL for a specific workflow, and open in a new tab, this gives a 404
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: