-
Notifications
You must be signed in to change notification settings - Fork 21
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
scala.reflect.internal.FatalError: class Object does not have a method getClass #13045
Comments
So we fail in
where I have to look a bit closer how But if "Restarting the presentation compiler doesn't help" that sounds like a different cause... |
I started getting it more often now, so I will try and connect debugger again. |
Which repo..? Does it happen randomly, or only after longer sessions? |
In the scalameta/metals repository, but some people reported it happen in other repositories. It seems to happen quite randomly, but at that point everything is broken. Might be connected to regenerating bloop config or switching branches a lot, but I could not make it reliably reproduce |
Ok it seems, everything in |
Seems possible.. It still didn't reproduce for me. Being able to debug it would be great.. |
I am trying out to run Metals on the same version as the project version to see if the problem ever happens without |
I am raising it here because I have no idea how this can happen. Restarting the presentation compiler doesn't help only restarting the whole JVM does. It's also not possible to reproduce it reliably.
What is more when debugging I managed at some point to find that getClass did exist, but it had no flags at all. Anyone has any idea how it's possible? Any hints or debugging advice would be welcome
Reproduction steps
I can't reproduce it reliably and it seems to happen more often a time especially on latests metals with 2.13.15.
Problem
Presentation compiler stops being possible to use
Error stacktrace:
scalac options
classpath
More about it in scalameta/metals#5272
The text was updated successfully, but these errors were encountered: