`gp await-port` doesn't work correctly when port is private
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
While testing https://twitter.com/gtsiolis/status/1417927681946103821?s=20
(https://gitpod.io/#https://gitlab.com/gitpod-io/gitlab/)
I was seeing this message in terminal, and it took forever
Awaiting port 3000... ok
Waiting for GitLab at https://3000-yellow-guineafowl-avf4hmmy.ws-us11.gitpod.io ...................
Changing port 3000 from private to public - fixes it right away.
Steps to reproduce
- Open https://gitpod.io/#https://gitlab.com/gitpod-io/gitlab/
- Wait for this kind of message in terminal
Awaiting port 3000... ok
Waiting for GitLab at https://3000-yellow-guineafowl-avf4hmmy.ws-us11.gitpod.io ...................
- Change port 3000 from private to public
- Confirm that terminal stopped waiting
Expected behavior
gp await 3000 should work the same when ports are set to private or public.
Example repository
https://gitpod.io/#https://gitlab.com/gitpod-io/gitlab/
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gp await-port/gp await 3000 command and reproduce the behavior using the linked GitLab example repository. Compare private and public port handling; done means gp await 3000 stops waiting correctly for both visibility settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100