Editor could not be opened for existing file

[Omcsesz]

Type: Bug

Hello, Team!

When clicking on an existing file with an error, I get the following error (see attachment). I am also able to reproduce the issue in the Insiders edition. Can you fix this?
EditorCouldNotBeOpened
EditorCouldNotBeOpenedLogWithTrace.txt

VS Code version: Code 1.74.3 (97dec17, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	undefined
Memory (System)	31.75GB (4.55GB free)
Process Argv	--crash-reporter-id c2d76645-3789-47da-a678-f1fbfbb015bc
Screen Reader	no
VM	0%

Extensions (36)

Extension	Author (truncated)	Version
project-manager	ale	12.7.0
ng-template	Ang	15.1.0
gitstash	art	5.1.0
asciidoctor-vscode	asc	2.9.8
vscode-tailwindcss	bra	0.9.6
npm-intellisense	chr	1.4.4
path-intellisense	chr	2.8.4
gitignore	cod	0.9.0
font-preview	ctc	2.2.1
vscode-eslint	dba	2.2.6
githistory	don	0.6.19
gitlens	eam	13.2.0
vscode-html-css	ecm	1.13.1
EditorConfig	Edi	0.16.4
prettier-vscode	esb	9.10.4
vscode-firefox-debug	fir	2.9.8
code-runner	for	0.12.0
angular-essentials	joh	13.0.0
Angular2	joh	13.0.0
vscode-peacock	joh	4.2.2
git-graph	mhu	1.30.0
vscode-scss	mrm	0.10.0
vscode-docker	ms-	1.23.3
csharp	ms-	1.25.2
remote-containers	ms-	0.266.1
material-icon-theme	PKi	4.23.1
tsimporter	pmn	2.0.1
vscode-xml	red	0.23.0
svg-preview	Sim	2.8.3
vscode-csstree	sme	1.1.0
sonarlint-vscode	Son	3.13.0
code-spell-checker	str	2.15.0
move-ts	str	1.12.0
vscode-icons	vsc	12.2.0
gitblame	wad	10.1.0
vscode-open-in-github	ziy	1.3.6

(1 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
pyind779:30647091
f6dab269:30613381

[mjbvz]

Please share a minimal project that demonstrates this issue so we can investigate

[Omcsesz]

@mjbvz Here it is:
frontend_.zip
Repro steps:

1. Open in VSCode
2. Run npm install
3. Run with "Debug Frontend Chrome" setting
4. When the popup window shows, choose "Show errors"
5. Try to open first file containing error (see attachment:
   EditorCouldNotBeOpenedMWE)

[mjbvz]

I believe this is an issue with your task configuration. You are currently using the normal tsc problem matcher but the error output is from ng serve which isn't compatible. That's why it's trying to open a file that starts with Error:

See angular/vscode-ng-language-service#625 for more info and some ideas on what to try

[Omcsesz]

@mjbvz I did the changes suggested on the page you referenced (I set the problem matcher), but it is still not working for in some cases (see attachment).
EditorCouldNotBeOpened_AfterSettingsDone

[mjbvz]

Please try asking on stack overflow or over in the angular extension