Features from the Browser not working: SCM, Run and Debug, Github #17375
Replies: 2 comments 2 replies
-
|
👋 Hi from Codespaces and thank you for the report. From your description, I suspect what happened is that the codespace ran into performance issues cloning down the repository— there was also an incident close to the time of this report, including degraded performance for Git Operations. However, if you were able to see and interact with the file tree within the browser editor during that time, that would rule this out. Glad to hear things worked well from VS Code on the desktop. Please let us know if you consistently see these problems from the web editor! We have codespaces running on infrastructure in West Europe, so unusually high latency would be unexpected. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for pursuing the problem.
The URL is:
https://github.com/codespaces/gdevacc12-codespacequickstart-q4v6rgp3x6gv
…On Sat, 28 May 2022 at 16:46, Jake Shorty ***@***.***> wrote:
Sorry to hear you're still encountering problems. Do you mind sharing the
web editor URL for one of the codespaces for which you're seeing this? It's
a safe URL to share, as only you can authenticate and connect to it, but it
will allow us to better look for errors in telemetry. I'll file an internal
issue with our team to investigate further.
—
Reply to this email directly, view it on GitHub
<#17375 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOW4IFTMFLLOAIHCAQGMADVMIWT3ANCNFSM5XDWTVBQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I tried the Codespaces quick start but some features using the web browser did not work.
From Visual code running locally on my PC, once Visual Code was authenticated (naturally), then it seemed like all the features worked fine. The VC Run/Debug default "Launch Chrome against localhost" which caught me out initially. Switching to "Run Script:start" everything worked fine.
Windows 11 21H2 Build: 22000.675 x64, Chrome: Version 101.0.4951.67 (Official Build) (64-bit), Visual Code: 1.67.2,
Beta Was this translation helpful? Give feedback.
All reactions