when trying to autocomplete in a java file I get "ENOPRO: No file system provider found for resource"

[adietish]

looks duplicate to continuedev/continue#4903

Steps:

1. ASSERT: have a freshly started vscode
2. ASSERT: have a java project opened in vscode (I am using a quarkus project "code-with-quarkus3")
3. EXEC: open a java file, remove some character (I removed the ";" in the end of the line)

Result:
I get an error notification with the following message:

ENOPRO: No file system provider found for resource `jdt://contents/java.base/java.lang/String.class?%3Dcode-with-quarkus3%2F%5C...`

[fbricon]

likely the same as continuedev/continue#3795 too.

Basically the problem is only vscode-java can resolve jdt:// URIs, sent by the JDT.LS. I believe Continue/Granite.Code issues LSP requests in certain cases, but the jdt:// uris are not resolvable directly, hence the error. I need to investigate.

[adietish]

Latest continue extension (I tested 1.0.7) wont display above error. In the logs I still a similar error though

mainThreadExtensionService.ts:79 Unavailable (FileSystemError): ENOPRO: No file system provider found for resource 'jdt://contents/microprofile-fault-tolerance-api-4.0.2.jar/org.eclipse.microprofile.faulttolerance/Timeout.class?%3Dcode-with-quarkus3%2F%5C%2FUsers%5C%2Fadietish%5C%2F.m2%5C%2Frepository%5C%2Forg%5C%2Feclipse%5C%2Fmicroprofile%5C%2Ffault-tolerance%5C%2Fmicroprofile-fault-tolerance-api%5C%2F4.0.2%5C%2Fmicroprofile-fault-tolerance-api-4.0.2.jar%3D%2Fmaven.pomderived%3D%2Ftrue%3D%2F%3D%2Fjavadoc_location%3D%2Fjar%3Afile%3A%5C%2FUsers%5C%2Fadietish%5C%2F.m2%5C%2Frepository%5C%2Forg%5C%2Feclipse%5C%2Fmicroprofile%5C%2Ffault-tolerance%5C%2Fmicroprofile-fault-tolerance-api%5C%2F4.0.2%5C%2Fmicroprofile-fault-tolerance-api-4.0.2-javadoc.jar%5C%21%5C%2F%3D%2F%3D%2Fmaven.groupId%3D%2Forg.eclipse.microprofile.fault-tolerance%3D%2F%3D%2Fmaven.artifactId%3D%2Fmicroprofile-fault-tolerance-api%3D%2F%3D%2Fmaven.version%3D%2F4.0.2%3D%2F%3D%2Fmaven.scope%3D%2Fcompile%3D%2F%3D%2Fmaven.pomderived%3D%2Ftrue%3D%2F%3Corg.eclipse.microprofile.faulttolerance%28Timeout.class'
	at Yi.e (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:18447)
	at Object.readFile (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:16562)
	at async _VsCodeIdeUtils.readRangeInFile (/Users/adietish/.vscode/extensions/continue.continue-1.0.7-darwin-arm64/out/extension.js:672196:11)
	at async /Users/adietish/.vscode/extensions/continue.continue-1.0.7-darwin-arm64/out/extension.js:133559:25
	at async Promise.all (index 0)
	at async _ImportDefinitionsService._getFileInfo (/Users/adietish/.vscode/extensions/continue.continue-1.0.7-darwin-arm64/out/extension.js:133556:60)
	at async PrecalculatedLruCache.initKey (/Users/adietish/.vscode/extensions/continue.continue-1.0.7-darwin-arm64/out/extension.js:131365:26)

[fbricon]

I managed to reproduce with the latest granite/customization branch, which contains the commit that should supposedly fix this issue. grrr

[fbricon]

PR opened upstream continuedev/continue#5536

[fbricon]

PR was merged upstream, we need to wait for granite.code to pick it up now

[fbricon]

Completed via Granite-Code/continue-for-granite#38, picking up the upstream fix.