FetchError when running under macOS with Apple Silicon / M1 - with solution #518
Replies: 3 comments
-
Thanks for contributing this! I can try to work it into the docs, although I'm not sure how fast that'll happen right now. In the meantime, I do have discussions enabled on the repo. Feel free to start a thread there! Leaving open for now, and updating as a docs item. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your response and your time! |
Beta Was this translation helpful? Give feedback.
-
Converted from an Issue to a discussion thread (which I just discovered). |
Beta Was this translation helpful? Give feedback.
-
Environment & Configuration:
First of all, thanks for the great extension! This is more intended as a Public Service Announcement, rather than an actual bug in the extension software, as the error is with languagetool, not with your extension. I was not sure where to post my solution though, and as I needed to do some digging to find the solution, I figured I should share my experiences.
Describe the bug
I installed LanguageTool with homebrew and ran the local languagetool server unter http://localhost:8081, as described in the wiki.
When installing the extension and linting some german text, the text didn't get linted and I noticed that the extension produced some errors in the output:
I looked at the log files of the LanguageTool server under
/opt/homebrew/var/log/languagetool/languagetool-server.log
and noticed some errors:... etc.
My Solution
After some digging, I found out that LanguageTool 5.9 uses a library, BridJ, which, at this point in time, has no binary built for arm64. See here.
Apparently, the error got fixed with the languagetool snapshot from 2022-11-26.
I then
After that, I found the
languagetool-server.jar
underlanguagetool-standalone/target/LanguageTool-6.0-SNAPSHOT/LanguageTool-6.0-SNAPSHOT
I then put the complete path to this jar file under VSCode Settings > Language Tool Linter > Managed > Jar File and set the service type under Settings > Language Tool Linter > Service Type to
managed
And voilà, now everything works as expected.
I am not sure if my solution was the most elegant, but it works, for me at least.
Sorry if this is the wrong place for this. Again, I was not sure where to put it for other m1 users who maybe get the same error to find it. Maybe there could be a place for it in the docs?
Beta Was this translation helpful? Give feedback.
All reactions