You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hit this issue with metals when navigation just stopped working silently. Bloop cli also was failing to compile project without any reason, only after I tried bloop compile --verbose --project I found what's the issue. Then I discovered plenty of directoties under each project's bloop-internal-classes, seems like bloop is not handling lifecycle of them.
Some time ago I saw a issue when someone was complaining about how much bloop is writing to the hard drive and I have to second that opinion.
This might cause the compiler to never work again until restart. It seems that the reason might be that one of the files is locked, but this is highly difficult to reproduce.
Connected to scalacenter#1989
This might cause the compiler to never work again until restart. It seems that the reason might be that one of the files is locked, but this is highly difficult to reproduce.
Connected to scalacenter#1989
This might cause the compiler to never work again until restart. It seems that the reason might be that one of the files is locked, but this is highly difficult to reproduce.
Connected to #1989
Hit this issue with metals when navigation just stopped working silently. Bloop cli also was failing to compile project without any reason, only after I tried
bloop compile --verbose --project
I found what's the issue. Then I discovered plenty of directoties under each project'sbloop-internal-classes
, seems like bloop is not handling lifecycle of them.Some time ago I saw a issue when someone was complaining about how much bloop is writing to the hard drive and I have to second that opinion.
Below I paste what I got from verbose logging:
The text was updated successfully, but these errors were encountered: