Keep getting "Unable to open <file>: File not found" when clicking on Problem links

[StephenWeatherford]

Issue Type: Bug

I'm not currently sure of an exact repro. If this issue is not known, I can try to come up with an exact repro. But this is happening quite a lot with at least my current project, but didn't used to happen before the recent update.

What's happening is that I'm getting a lot of problems that don't go away even when fixed, and clicking on it gives the error "Unable to open …: File not found", and asks if I want to create the file. But the file does in fact exist.

The only way I know of to get rid of them is restarting vscode.

Still repros with all extensions disabled.

VS Code version: Code 1.23.1 (d0182c3, 2018-05-10T17:11:17.614Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel(R) Xeon(R) CPU E31230 @ 3.20GHz (4 x 3193)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled
Memory (System)	15.96GB (5.48GB free)
Process Argv	C:\Program Files\Microsoft VS Code\Code.exe C:\Repos\vscode-azurestorage
Screen Reader	no
VM	0%

Extensions (22)

Extension	Author (truncated)	Version
mongogo	bag	0.1.2
regex	chr	0.2.0
vscode-markdownlint	Dav	0.17.0
githistory	don	0.4.1
jupyter	don	1.1.4
tslint	eg2	1.0.29
vscode-bump	fab	1.5.1
docthis	joe	0.6.0
vscode-antlr4	mik	2.0.3
vscode-azureappservice	ms-	0.8.1
vscode-azurefunctions	ms-	0.9.1
vscode-azurestorage	ms-	0.3.1
vscode-cosmosdb	ms-	0.7.1
python	ms-	2018.4.0
azure-account	ms-	0.4.0
csharp	ms-	1.15.2
azurerm-vscode-tools	msa	0.4.2
vscode-versionlens	pfl	0.21.0
yo	sam	0.9.3
extension-api	spy	0.3.0
python	tht	0.2.3
code-lens-roundup	wad	1.0.0

[StephenWeatherford]

[mjbvz]

Are these errors coming from the editor or from a problem matcher in a build task?

[StephenWeatherford]

@mjbvz How do I tell? I'm guessing problem matcher, it's a standard NodeJS project (a VS extension), here's my tasks.json:

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "npm",
            "script": "watch",
            "problemMatcher": "$tsc-watch",
            "isBackground": true,
            "presentation": {
                "reveal": "never"
            },
            "group": {
                "kind": "build",
                "isDefault": true
            }
        },
        {
            "type": "npm",
            "script": "lint",
            "problemMatcher": {
                "base": "$tslint5",
                "fileLocation": "absolute"
            }
        }
    ]
}

[mjbvz]

When do the errors show up? When you open a file or when you start the build task?

Also, do you see this in vs code insiders?

[StephenWeatherford]

I think a problem matcher. The links work fine at first, it's only after I've done some coding (maybe debugging) that they stop linking correctly and don't go away.

Repros in Insiders as well.

[dbaeumer]

@StephenWeatherford best would be to provide a GitHub repository we can clone that demos this. I looked at the screen shot and the file path actually does look fine to me.

[StephenWeatherford]

Yes, the file path always looks fine but still won't open. I'll try to get a repo repro. :-)