Project import failed when there's spaces in project name

[Eyre-S]

Describe the bug

1. Open a project which names have spaces.

2. Import the project

3. Bloop files generated normally, but Metals will report errors

2023.10.13 11:21:45 INFO  Connected to Build server: Bloop v1.5.11
2023.10.13 11:21:45 ERROR Build server error: No project associated with Uri(file:/S:/workspace/Coeur%20Morny%20Cono/?id=Coeur%20Morny%20Cono-test)
2023.10.13 11:21:45 INFO  time: Imported build in 0.28s
2023.10.13 11:21:46 INFO  skipping build import with status 'Installed'
2023.10.13 11:21:49 INFO  time: indexed workspace in 3.47s
2023.10.13 11:21:49 INFO  {
  "jsonrpc": "2.0",
  "id": "9",
  "error": {
    "code": -32600,
    "message": "No project associated with Uri(file:/S:/workspace/Coeur%20Morny%20Cono/?id\u003dCoeur%20Morny%20Cono-test)"
  }
}

Expected behavior

Expected import succeed.

Operating system

Windows

Editor/Extension

VS Code

Version of Metals

1.0.1+103-cc897ef4-SNAPSHOT

Extra context or search terms

I have tested that removing spaces in the path and project name will make Metals works fine.

[tgodzik]

Thanks for reporting! This is really curious as we do have tests for that exact scenario and we did fix this multiple times :/ Will need to look into this yet again.

[tgodzik]

Ok, so if anyone looks at this, the issue seems connected strictly to the Bloop gradle integration and how spaces are handled there. There is a difference between Bloop server itself and bloop-gradle