-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Bug] asExternalUri never returns #14248
Comments
@jeromelaban seems to be working for me, can you still reproduce? also not sure what you mean regarding the code-server PR you linked, Gitpod does not use code-server.
|
Hi @jeanp413! We published a workaround for it in our v0.5.1, but if you install the version 0.4.0 of the addin, it should reproduce. As for the code-server PR, my apologies if it's unrelated. I don't really understand yet the relations between all the pieces of gitpod's ecosystem :) |
Small repro:
@mustard-mh maybe related to some optimizations we did about not firing event for ports, this logic is always returning false |
Thanks! |
@jeromelaban it's not deployed yet 🙏 , will ping you if we are going to deploy it to SaaS Gitpod |
Sorry for being late, it's been deployed to production SaaS Gitpod. @jeromelaban |
Bug description
Since what I think is coder/code-server#5624, awaiting
vscode.env.asExternalUri(vscode.Uri.parse("http://localhost:12345");
never returns.Steps to reproduce
I don't have a simple repro available, but the promise awaiting
vscode.env.asExternalUri
does not return.Here's an larger repro:
MyApp.Wasm
projectvscode.env.asExternalUri
works, the output forUno Platform - Hot Reload
will showApplication started. Press Ctrl+C to shut down.
.Currently, that message does not appear.
Workspace affected
No response
Expected behavior
A new listening port is opened based on the external uri.
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: