Skip to content

port-forward button doesn't appear automatically unless we do a refresh #8834

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.

Sign up for GitHub

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

Jump to bottom
Closed
matifali opened this issue Aug 1, 2023 · 7 comments
Closed

port-forward button doesn't appear automatically unless we do a refresh #8834

matifali opened this issue Aug 1, 2023 · 7 comments
Assignees
@BrunoQuaresma
Labels
s2 Broken use cases or features (with a workaround). Only humans may set this. site Area: frontend dashboard

Comments

@matifali
Copy link
Member

matifali commented Aug 1, 2023

I have experienced this on a new helm deployment.
Please take a look at the attached video.

port-forward-button-doesn.t-appear.mp4
@matifali matifali added site Area: frontend dashboard s2 Broken use cases or features (with a workaround). Only humans may set this. bug labels Aug 1, 2023
@sharkymark
Copy link
Contributor

Is that a cookie thing (dev URL, I mean port forward not being created initially)?

@matifali
Copy link
Member Author

matifali commented Aug 1, 2023

@sharkymark I am not sure. Have you seen this anytime?

@BrunoQuaresma
Copy link
Collaborator

@matifali this is probably fixed. Feel free to reopen if you still seeing it.

@matifali
Copy link
Member Author

matifali commented Aug 9, 2023

On the latest main, I can still see this. It needs to refresh the page for the button to appear.

@matifali matifali reopened this Aug 9, 2023
@BrunoQuaresma
Copy link
Collaborator

Is this workspace on dev.coder.com?

@matifali
Copy link
Member Author

matifali commented Aug 9, 2023

@BrunoQuaresma This is on a PR deployment and only happens when the deployment is new. A refresh brings it back and also for subsequent workspaces, it does show as normal. The screen recording above explains it.

This was referenced Aug 14, 2023
Closed
Closed
@bpmct
Copy link
Member

bpmct commented Aug 25, 2023

This has been fixed! Just tried on a new PR deployment

@bpmct bpmct closed this as completed Aug 25, 2023
@BrunoQuaresma BrunoQuaresma self-assigned this Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BrunoQuaresma BrunoQuaresma

Labels
s2 Broken use cases or features (with a workaround). Only humans may set this. site Area: frontend dashboard
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sharkymark @BrunoQuaresma @matifali @bpmct