References to another project causing issues in current project (stale Bloop stuff?) #5279
Labels
bug
Something that is making a piece of functionality unusable
upstream-fix-needed
Waiting on a fix upstream
Describe the bug
So I originally hit on a very similiar issue to this with scala-cli and created an issue for it here, although I'm starting to think the issue actually lays deeper in Bloop. I'll create here to try and diagnose whether it's an issue with Bloop or maybe with Metals somehow, but my gut tells me Bloop.
The issue I linked about hints at Bloop holding onto some stale state and this seems to be the same case again. It's hard to reproduce, but let me outline how this happened for me. I was working on the coursier codebase and triggered a full clean compile. When looking at the logs I saw:
Notice that right between the logs about certain modules being compiled I get an error thrown by the build server about a URI found in my local dotty codebase. That project isn't open, and shouldn't be appearing in the workspace logs of another project.
Expected behavior
I would never expect any reference to another project to appear and be causing issue in another project.
Operating system
macOS
Editor/Extension
Nvim (nvim-metals)
Version of Metals
0.11.12+77-cce28f19-SNAPSHOT
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered: