Open bjtho08 opened 11 months ago
Replicated on version v1.14.0
on Mac
Version: 1.84.0-insider (Universal)
Commit: 874831ebcf088f59735879156f62308ce48f17d1
Date: 2023-10-06T19:18:47.163Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.0.0
Same here, version v1.14.0
on Cursor
Version: 0.21.1
VSCode Version: 1.84.2
Commit: 1a7903c409e3e915db28f4c124497660066e85a0
Date: 2023-12-30T03:05:39.344Z (1 wk ago)
Electron: 25.9.2
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.2.0
I am experiencing this on m1 mac, with VSCodium
extension:
Name: YAML
Id: redhat.vscode-yaml
Description: YAML Language Support by Red Hat, with built-in Kubernetes syntax support
Version: 1.15.0
Publisher: redhat
VS Marketplace Link: https://open-vsx.org/vscode/item?itemName=redhat.vscode-yaml
codium:
Version: 1.88.1
Release: 24104
Commit: 0d01a72525276e5e3771fe5851b9c83de0de1e2b
Date: 2024-04-13T01:43:30.924Z (2 mos ago)
Electron: 28.2.8
ElectronBuildId: undefined
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
Describe the bug
The extension is attempting to access a resource scoped configuration without actually providing a resource. The extension host log gives the following two lines:
This issue is identical to #478, which also appears to outline the way to fix the still-present issue.
Environment
I am running v1.14.0 of the extension in VSCode 1.82.1.