Fix long running tests in support of migration to esbuild#1081
Open
MicroFish91 wants to merge 28 commits into
Open
Fix long running tests in support of migration to esbuild#1081MicroFish91 wants to merge 28 commits into
MicroFish91 wants to merge 28 commits into
Conversation
MicroFish91
changed the title
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
MicroFish91
commented
May 19, 2026
| ".vscode-test": true | ||
| } | ||
| }, | ||
| "js/ts.tsdk.path": "node_modules/typescript/lib", |
Contributor
Author
There was a problem hiding this comment.
Fixes the mocha warnings that have been showing up
| return { | ||
| name: localize('containerAppEnvironment', 'Container Apps Environment'), | ||
| value: nonNullValueAndProp(context.managedEnvironment, 'name'), | ||
| value: context.managedEnvironment?.name ?? context.newManagedEnvironmentName ?? '', |
Contributor
Author
There was a problem hiding this comment.
Note for future confirmation views - we should prefer optionals over nonNull for these sections, I think it can still run when users select to create a new resource, in which case it could still be undefined when this gets run
The native FC_* env var support in vscode-azureresourcegroups v0.12.7 has issues when relying solely on the logIn command path: - setOverrideAzureSubscriptionProvider bypasses tree provider caching (checked fresh on every call), while the native path caches the subscription provider on first access - If the tree renders before logIn completes, it may cache a stale/unsigned-in provider instance - The alpha auth dependency may also have timing issues with signIn() under the native factory flow Until the native path is stable, explicitly override the subscription provider via the RG test API. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
MicroFish91
force-pushed
the
mwf/inc-lime
branch
from
b88a4b7 to
7bd4a72
Compare
Contributor
Author
|
Going to go ahead and take this out of draft so people can review. I did verify that it passes remotely, but ever since they expanded our quota, we've still been getting intermittent restrictions which I messaged them about: 
Just a heads up as you might notice that in some of the pipeline runs |
bwateratmsft
approved these changes
Jun 16, 2026
bwateratmsft
left a comment
bwateratmsft
left a comment
Contributor
There was a problem hiding this comment.
Looks good but see my chat message about the Mocha warnings
bwateratmsft
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tests are now updated to be compatible with the ES build work. I also fixed a few smaller issues that cropped up since the tests hadn’t been running for a while.
One annoying change: I used to just delete the .vscode/ folder in each project between deployments and that worked just fine... but that’s apparently no longer enough. I assume a newer VS Code update introduced some kind of caching behavior that now has to be explicitly reset through the API; otherwise deployments can still pick up older cached settings even if the folder was deleted.
Update: The remote subscription we use only seems to support 1 container environment so I'm requesting an increase in quotas before I do a final verification pass