redhat-developer / redhat-developer/vscode-quarkus

qute/template/isInTemplate unable to gracefully handle certain files

Open
#1,008 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

qute
Dominant language
TypeScript
Stars
79
Forks
31
Avg merge
12h 51m
Merged PRs (30d)
6

Description

Yes, the error log indicates this is going into quarkus-ls at https://github.com/redhat-developer/quarkus-ls/blob/3aaef2d88ae703b069501709db6b266273244efb/qute.jdt/com.redhat.qute.jdt/src/main/java/com/redhat/qute/jdt/internal/ls/QuteSupportForTemplateDelegateCommandHandler.java#L121 but I'm guessing this comes from https://github.com/redhat-developer/vscode-quarkus/blob/61333f1008cafb70fcaf960e71996bc581e37fc6/src/qute/commands/registerCommands.ts#L247 . We may need to be a bit more selective about what documents get sent or handle it more gracefully server-side.

!ENTRY org.eclipse.jdt.ls.core 4 0 2025-04-17 12:21:26.780
!MESSAGE Failed to resolve VIEW_DOCUMENT_SCHEME:/ssw-certificato.outbox%3A%227a74eaab-cb9c-4f1d-9e71-114352bce3b8%22.json?%3Fnamespace%3Dssw-certificato.outbox%26connectionId%3D7aa11cce-907c-4eeb-ace6-4aca5d205ef9%26documentId%3Da8cdc3af-c6d8-4d0b-ad0e-c7cc46dba313%26source%3Dtreeview
!STACK 0
java.net.URISyntaxException: Illegal character in scheme name at index 4: VIEW_DOCUMENT_SCHEME:/ssw-certificato.outbox%3A%227a74eaab-cb9c-4f1d-9e71-114352bce3b8%22.json?%3Fnamespace%3Dssw-certificato.outbox%26connectionId%3D7aa11cce-907c-4eeb-ace6-4aca5d205ef9%26documentId%3Da8cdc3af-c6d8-4d0b-ad0e-c7cc46dba313%26source%3Dtreeview
	at java.base/java.net.URI$Parser.fail(URI.java:2995)
	at java.base/java.net.URI$Parser.checkChars(URI.java:3166)
	at java.base/java.net.URI$Parser.parse(URI.java:3192)
	at java.base/java.net.URI.<init>(URI.java:645)
	at org.eclipse.jdt.ls.core.internal.JDTUtils.toURI(JDTUtils.java:1194)
	at org.eclipse.jdt.ls.core.internal.JDTUtils.findFile(JDTUtils.java:1121)
	at com.redhat.qute.jdt.internal.ls.JDTUtilsLSImpl.findFile(JDTUtilsLSImpl.java:60)
	at com.redhat.qute.jdt.QuteSupportForTemplate.findProject(QuteSupportForTemplate.java:418)
	at com.redhat.qute.jdt.QuteSupportForTemplate.findJavaProject(QuteSupportForTemplate.java:397)
	at com.redhat.qute.jdt.QuteSupportForTemplate.getProjectInfo(QuteSupportForTemplate.java:135)
	at com.redhat.qute.jdt.internal.ls.QuteSupportForTemplateDelegateCommandHandler.isInTemplate(QuteSupportForTemplateDelegateCommandHandler.java:463)
	at com.redhat.qute.jdt.internal.ls.QuteSupportForTemplateDelegateCommandHandler.executeCommand(QuteSupportForTemplateDelegateCommandHandler.java:121)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:611)
	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)

!ENTRY org.eclipse.jdt.ls.core 4 2 2025-04-17 12:21:26.781
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ls.core".
!STACK 0
java.lang.NullPointerException: Cannot invoke "java.net.URI.getScheme()" because "uri" is null
	at org.eclipse.core.runtime.URIUtil.isFileURI(URIUtil.java:188)
	at com.redhat.qute.jdt.QuteSupportForTemplate.findProject(QuteSupportForTemplate.java:426)
	at com.redhat.qute.jdt.QuteSupportForTemplate.findJavaProject(QuteSupportForTemplate.java:397)
	at com.redhat.qute.jdt.QuteSupportForTemplate.getProjectInfo(QuteSupportForTemplate.java:135)
	at com.redhat.qute.jdt.internal.ls.QuteSupportForTemplateDelegateCommandHandler.isInTemplate(QuteSupportForTemplateDelegateCommandHandler.java:463)
	at com.redhat.qute.jdt.internal.ls.QuteSupportForTemplateDelegateCommandHandler.executeCommand(QuteSupportForTemplateDelegateCommandHandler.java:121)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:611)
	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.