This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 656
🐛 error: no bin target named rome_lsp
#3138
Labels
S-To triage
Status: user report of a possible bug that needs to be triaged
Comments
lgarron
added
the
S-To triage
Status: user report of a possible bug that needs to be triaged
label
Aug 31, 2022
It seems that tools/.github/workflows/release_lsp.yml Line 105 in de04db1
This works, but doesn't create a binary.
Taken from |
lgarron
changed the title
🐛
🐛 Aug 31, 2022
error: no bin target named
rome_lsp``error: no bin target named
rome_lsp`
lgarron
changed the title
🐛
🐛 Aug 31, 2022
error: no bin target named
rome_lsp`error: no bin target named rome_lsp
lgarron
changed the title
🐛
🐛 Aug 31, 2022
error: no bin target named rome_lsp
error: no bin target named
rome_lsp`
lgarron
changed the title
🐛
🐛 error: no bin target named Aug 31, 2022
error: no bin target named
rome_lsp`rome_lsp
There's a PR to update that section. #3136 |
Also, if you're now using the built binary, you can now inspect the logs: https://rome.github.io/tools/rome_bin/index.html#logs |
The section has been updated! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to follow https://github.com/rome/tools/blob/main/CONTRIBUTING.md#language-server-and-vs-code-extension-development so I can test #3089 and #3088 (without waiting a week).
Environment information
What happened?
git clone https://github.com/rome/tools cd tools cargo build --bin rome_lsp
Result:
Expected result
The instructions result in a
rome_lsp
binary.Note that
cargo build --bin rome
works — it's only therome_lsp
target that fails for me.Code of Conduct
The text was updated successfully, but these errors were encountered: