-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Test: ESM exploration builds #226399
Comments
https://builds.code.visualstudio.com/builds/exploration looks like staff only.
|
Thanks for willing to test! Here are direct links:
|
Thank you for providing a newer build. |
To clarify: we did not change anything for extensions, this is core only! |
I know the impact on extensions is just a side effect. |
Technically probably yes, but entirely out of the scope of this issue and not in the near future I think. |
That's disappointing, but I hope the fix of this issue make it easier (or possible directly possible) to allow extensions consume ESM code. I try this build for everyday use for a while. |
The following error occurs sometimes when trying to install extensions:
However, I was able to install them at the second trial.
|
Please see if you can reproduce with insiders as well or not. |
I installed the latest Insiders and tried installing some extensions, but no "fetch failed" has occurred. |
If someone has trouble getting remote to work with exploration builds, https://builds.code.visualstudio.com/builds/insider?commit=4edd1ad59d7e15a3c08e7111f00a2cf3785bbe87&dev=true is an insiders build that is ESM enabled, but you need to disable auto update if you plan on using that. |
Everything looks good from my side- just need to check if telemetry is ingested correctly. Since there is an ingestion delay, I'll wait a few hours and then check back. |
I verified by setting the log level to trace and that I saw telemetry events emitted in the output channel. How do I confirm that events were received on our end (besides looking for my events in our telemetry pipeline once they are ingested). Otherwise, everything looks good on |
@bhavyaus you check for a specific event using kusto |
Example: create a file with your name as the extension. Then:
I still get a network error when I try this, so will wait a little longer. |
@meganrogge if you are getting a network error in the kusto window, you now are supposed to be on the azure vpn to access that data. I haven't set that up, I just use a devbox. |
I will keep selfhosting |
Refs: #160416
Complexity: 5
Authors: @jrieken @bpasero
Roles: Developer
Create Issue
Setup: Desktop / Remote
ff7a154d5e5e9034914f0466420f0f1407f0c95e
Setup: Web
vscode-version=<commit>
: to point to the ESM enabled web bitsvscode-esm=true
: to enable the server to serve ESM web bitsTesting
This is about exploratory testing all aspects of the build and checking for:
Areas to cover:
The text was updated successfully, but these errors were encountered: