Skip to content
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

Pin core tools to fix tests #4310

Merged
merged 2 commits into from
Nov 1, 2024
Merged

Pin core tools to fix tests #4310

merged 2 commits into from
Nov 1, 2024

Conversation

alexweininger
Copy link
Member

Temporarily pin core tools to an older version to fix CI tests. There must be a breaking change in a recent version. I couldn't just change it to v4 instead of v4-prerelease since both tags point to the same version.

image

See #4299 (comment) for more context. Thanks @captainsafia for the help!

@alexweininger alexweininger requested a review from a team as a code owner November 1, 2024 19:13
@alexweininger alexweininger changed the title Alex/gulp Pin core tools to fix tests Nov 1, 2024
@alexweininger alexweininger merged commit 1912ed7 into nat/startFuncApi Nov 1, 2024
2 checks passed
@alexweininger alexweininger deleted the alex/gulp branch November 1, 2024 19:17
alexweininger added a commit that referenced this pull request Nov 4, 2024
…installed (#4299)

* Add an API command to start a func task and to check if CLI tools is installed

* Make some updates for isFuncCoreToolsInstalled

* Update apiVersion

* Update apiVersion to minor path

* Use fully qualified path rather than relative

* Use Uri.fspath as key for FuncRunningMap/Port (#4309)

* Use Uri.fspath as key for FuncRunningMap/Port

This commit modifies pickFuncProcess startFuncProcessFromApi removing
the workspaceFolder requirement and adding in the environment variables.

funcHostTask was originally tracked by vscode.WorkspaceFolder via
Task.Scope and DebugConfiguration.WorkspaceFolder. This commit modifies
it to use a new AzureFunctionTaskDefinition.functionsApp property which
is either the `buildPath` from startFuncProcessFromApi or the
vscode.WorkspaceFolder.uri.fsPath to maintain backwards compatibility.

runningFuncTaskMap, funcTaskStartedEmitter, and runningFuncPortMap now
all using the vscode.Uri.fsPath string which can be used to map back to
a WorkspaceFolder. However in the cases the WorkspaceFolder fails, APIs
that used it will now see undefined passed in.

* Make unique 'type' so VS Code will launch multiple tasks

* Address Comments

* Pin core tools to fix tests (#4310)

* Try stable v4 feed

* Fixup

---------

Co-authored-by: Andrew Wang <[email protected]>
Co-authored-by: Alex Weininger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant