-
Notifications
You must be signed in to change notification settings - Fork 354
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
My student's project complete crash and burn with Metals and VSCode #4837
Comments
Thanks for reporting! I will take a look through the logs, but I see that they managed to find a wealth of issues while using Metals 😨
I also see an error with troubles to load jars required by Metals or bsp server, did the student clear their caches at some point? This might sometimes break more than fixed. Most of that we should be able to fix, sorry about the issues :/ |
This may be due to my attempt of using the student's project on my computer to see if I also experience bugs |
looks like this is using a release candidate of scala, maybe going back to the last real release helps? |
For scalameta#4837 There are some other places that access span, but most of them seem safe.
Previously, the exception could break anthing trying to use Trees and since it's an error in the parser we shouldn't break metals. Now, we catch the exception instead and print the code it failed on. Related to scalameta#4837
For #4837 There are some other places that access span, but most of them seem safe.
Ok I think I tackled most issues, I will close this one, we can reopen when another set of issues appears. |
@tgodzik Thank you very much for doing this! |
Previously, the exception could break anthing trying to use Trees and since it's an error in the parser we shouldn't break metals. Now, we catch the exception instead and print the code it failed on. Related to #4837
Describe the bug
I'll first say I'm not here to whine about metals/bloop. The current state of Scala tooling is waaaaaaay better than where I started. But when I (and my students) try to use metals, we hit so many issues that I'm just giving up and using sbt in terminal directly.
I opened this issue to continue the discussion with @ckipp01 from
https://contributors.scala-lang.org/t/revisiting-the-default-build-server-for-metals-roadmap/6054
I took it upon myself to no longer sweep the bugs under the carpet and try to report as much as I can.
Here is a recent log from my student's project. I edited it a little and removed identifying information.
I can send a zip file with the project privately, but it is still difficult to replicate issues that happen during regular project usage.
metals.log
What can we do to help finally isolate and fix these issues?
Expected behavior
No response
Operating system
Windows
Editor/Extension
VS Code
Version of Metals
0.11.9
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered: