Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checking "!}" or "?}" with LanguageTool premium server in French. #292

Open
Force789 opened this issue Jan 4, 2024 · 0 comments
Open

Checking "!}" or "?}" with LanguageTool premium server in French. #292

Force789 opened this issue Jan 4, 2024 · 0 comments
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label)

Comments

@Force789
Copy link

Force789 commented Jan 4, 2024

Describe the bug

The language server crashes when using the French language, with LanguageTool premium service when typing the following pattern ?} or !}

Steps to reproduce

Check any latex text with "?}" or "!}"

Expected behavior
Should pass without any crash. (working when set to English-US)

Sample document

\documentclass{article}

\begin{document}

Je fais des fotes !
\section{huh ?}

\end{document}

LTeX configuration

The base config with credentials for LanguageTool premium and set in French

LTeX LS log

GRAVE: LanguageTool failed. The following exception occurred:
java.lang.NullPointerException
	at org.bsplines.ltexls.languagetool.LanguageToolRuleMatch$Companion.fromLanguageTool(LanguageToolRuleMatch.kt:71)
	at org.bsplines.ltexls.languagetool.LanguageToolHttpInterface.checkInternal(LanguageToolHttpInterface.kt:96)
	at org.bsplines.ltexls.languagetool.LanguageToolInterface.check(LanguageToolInterface.kt:22)
	at org.bsplines.ltexls.server.DocumentChecker.checkAnnotatedTextFragment(DocumentChecker.kt:138)
	at org.bsplines.ltexls.server.DocumentChecker.checkAnnotatedTextFragments(DocumentChecker.kt:91)
	at org.bsplines.ltexls.server.DocumentChecker.check(DocumentChecker.kt:279)
	at org.bsplines.ltexls.server.LtexTextDocumentItem.check(LtexTextDocumentItem.kt:413)
	at org.bsplines.ltexls.server.LtexTextDocumentItem.checkAndGetDiagnostics(LtexTextDocumentItem.kt:295)
	at org.bsplines.ltexls.server.LtexTextDocumentItem.checkAndPublishDiagnostics(LtexTextDocumentItem.kt:272)
	at org.bsplines.ltexls.server.LtexTextDocumentItem.checkAndPublishDiagnosticsWithoutCache(LtexTextDocumentItem.kt:267)
	at org.bsplines.ltexls.server.LtexTextDocumentItem.checkAndPublishDiagnosticsWithoutCache$default(LtexTextDocumentItem.kt:266)
	at org.bsplines.ltexls.server.LtexTextDocumentService.didSave$lambda-2(LtexTextDocumentService.kt:197)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

Version information
List here the version information of the relevant software.

  • Operating system: Arch Linux
  • ltex-ls: 16.0.0
  • Java: 21

Extra info

It can be mitigated by adding a space between ?/! and }

@Force789 Force789 added 1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label) labels Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-bug 🐛 Issue type: Bug report (something isn't working as expected) 2-unconfirmed Issue status: Bug that needs to be reproduced (all new bugs have this label)
Projects
None yet
Development

No branches or pull requests

1 participant