You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described more thoroughly in this Discord thread, I observe that the command following gp ports await or gp open in a task does not run. In the case of gp ports await, the port is bound and the gp ports await seems to acknowledge this with an "OK" message, as per this screenshot, but the gp preview command that follows it does not seem to get executed because the page that it should display is not visible in the workspace even several minutes later.
This is not limited to gp ports await because I observe similar behavior with gp open, specifically in this task of my .gitpod.yml file. The README.md file does not open and the terminal does not exit.
In both cases, though, the commands will eventually behave as expected if the user clicks to set focus within the browser's viewport. That's not an obvious workaround though, and most users would likely conclude that the workspace didn't initialize properly and just give up.
Steps to reproduce
In Safari or Google Chrome (I've reproduced this in both, but have not tested other browsers):
Wait for several minutes and observe that neither the Web app on port 80 nor the README.md file was displayed as it should have been
Click around within the browser window's viewport and there's a good chance that doing so will cause both the Web app on port 80 and the README.md file to finally be shown
This seems to be an intermittent problem, but it happens almost all of the time.
Workspace affected
No response
Expected behavior
Should display a preview of the README file on the left of the main workspace area and the embedded browser to its right
Bug description
As described more thoroughly in this Discord thread, I observe that the command following
gp ports await
orgp open
in a task does not run. In the case ofgp ports await
, the port is bound and thegp ports await
seems to acknowledge this with an "OK" message, as per this screenshot, but thegp preview command
that follows it does not seem to get executed because the page that it should display is not visible in the workspace even several minutes later.This is not limited to
gp ports await
because I observe similar behavior withgp open
, specifically in this task of my .gitpod.yml file. TheREADME.md
file does not open and the terminal does not exit.In both cases, though, the commands will eventually behave as expected if the user clicks to set focus within the browser's viewport. That's not an obvious workaround though, and most users would likely conclude that the workspace didn't initialize properly and just give up.
Steps to reproduce
In Safari or Google Chrome (I've reproduced this in both, but have not tested other browsers):
README.md
file was displayed as it should have beenREADME.md
file to finally be shownThis seems to be an intermittent problem, but it happens almost all of the time.
Workspace affected
No response
Expected behavior
Should display a preview of the README file on the left of the main workspace area and the embedded browser to its right
Example repository
Click this link to launch the workspace.
The
.gitpod.yml
file [https://github.com/temporalio/edu-102-go-code/blob/t102-go-maintenance-202403/.gitpod.yml](is here).Anything else?
No response
The text was updated successfully, but these errors were encountered: