Skip to content

bug: fix path resolution to use resolved environment directly from settings #1926

bug: fix path resolution to use resolved environment directly from settings

bug: fix path resolution to use resolved environment directly from settings #1926

Triggered via pull request February 13, 2026 16:19
Status Failure
Total duration 13m 52s
Artifacts 1

pr-check.yml

on: pull_request
Create VSIX
33s
Create VSIX
Matrix: TypeScript Unit Tests
Matrix: Smoke Tests
Matrix: E2E Tests
Matrix: Integration Tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
TypeScript Unit Tests (ubuntu-latest)
Process completed with exit code 3.
TypeScript Unit Tests (windows-latest)
Process completed with exit code 1.
Lint: src/test/features/projectManager.initialize.unit.test.ts#L351
Expected { after 'if' condition
Lint: src/test/features/projectManager.initialize.unit.test.ts#L350
Expected { after 'if' condition
Lint: src/test/features/projectManager.initialize.unit.test.ts#L314
Expected { after 'if' condition
Lint: src/test/features/projectManager.initialize.unit.test.ts#L313
Expected { after 'if' condition

Artifacts

Produced during runtime
Name Size Digest
vsix Expired
1.29 MB
sha256:17e419adb3287da9c018c00e48fc77b513a45cde0c2e896478201d973891ca3e