In hosted-instance-log: "TypeError: Cannot read property 'path' of undefined" from vscode-builtin-json-language-feature
See original GitHub issueDescribe the bug
stack error in hosted-instance-log when staring a workspace:
Extension-Host:Promise rejection not handled in one second: TypeError: Cannot read property 'path' of undefined , reason: TypeError: Cannot read property 'path' of undefined
Extension-Host:With stack trace: TypeError: Cannot read property 'path' of undefined
at Object.a [as joinPath] (/default-theia-plugins/vscode-builtin-json-language-features/extension/client/dist/node/jsonClientMain.js:1:248754)
at /default-theia-plugins/vscode-builtin-json-language-features/extension/client/dist/node/jsonClientMain.js:1:116514
at Array.forEach (<anonymous>)
at /default-theia-plugins/vscode-builtin-json-language-features/extension/client/dist/node/jsonClientMain.js:1:116371
at Array.forEach (<anonymous>)
at f (/default-theia-plugins/vscode-builtin-json-language-features/extension/client/dist/node/jsonClientMain.js:1:116229)
at /default-theia-plugins/vscode-builtin-json-language-features/extension/client/dist/node/jsonClientMain.js:1:122454
Che version
- latest
- nightly
- other: please specify 7.28.0
Steps to reproduce
- Start Camel K stack
- look inside the hosted-instance-log output
Expected behavior
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl
- provide a full command that was used to deploy Eclipse Che (including the output)
- provide an output of
chectl version
command
- OperatorHub
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- Dev Sandbox (workspaces.openshift.com)
- other: please specify
Eclipse Che Logs
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
cannot read property 'path' of undefined - Stack Overflow
I managed to upload the files but unable to get the file path. router.post('/uploadFile',function(req,res,next){ if ...
Read more >TypeError: Cannot read property 'path' of undefined #26460
I am trying to migrate Theia monorepo to project references: https://github.com/theia-ide/theia/pull/2563/files But it fails during the ...
Read more >Cannot read property 'path' of null while installing apigeedm
Solved: Hi, I am using Windows OS. I want to deploy multiple proxies at same time in apigee edge so i am using...
Read more >Cannot Read Property of Undefined in JavaScript - Rollbar
TypeError : Cannot read property of undefined occurs when a property is read or a function is called on an undefined variable.
Read more >Cannot read property 'path' of undefined - Radzen IDE (Angular)
Hello, i receive an error when opening an edit or add dialog. I already have other add/edit pages, those work correctly.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I implemented the
extensionURI
stuff. However, when I open apackage.json
in the editor, I get an error message complaining it can’t load the schema from a uri like 'combinedschema://schemaservice/chepluginresource:/…`. It seems the json language service living at https://github.com/microsoft/vscode-json-languageservice gets its knickers in a twist on some non-standard URI’s, see for example https://github.com/microsoft/vscode/issues/115419. Note that the issue has been closed very recently, so this might be fixed in a new version of the plugin than what we have.if you have no error in log, yes