-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Go support not working at all #4471
Comments
@nikitavoloboev Thanks for sharing the issue! I found that this repo worked for me when I opened it in Zed: I am worried that there must be something different between our computers causing this. To help us debug, would you mind opening this repo, and then doing |
https://gist.github.com/nikitavoloboev/5be6fb1411bb857dcce7156c7fa3cc80 here it is I got the logs after doing this in a file |
Bizarre. Thanks for checking.
Is the language set to Go in the buffer?
Conrad
…On Tue, Sep 19, 2023 at 1:37 AM, Nikita ***@***.***> wrote:
@ConradIrwin <https://github.com/ConradIrwin>
I think Go language server never got started as I don't see it here.
[image: image]
<https://user-images.githubusercontent.com/6391776/268876885-35791731-a1a3-4c53-8f24-c746dffef187.png>
—
Reply to this email directly, view it on GitHub
<#4471>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAXAQHGLDKM34GOY3XBGK3X3FDULANCNFSM6AAAAAA42ZNFBM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think that means I need to create a go workspaces file at |
@nikitavoloboev thanks for the screenshot! This is caused by a poor handling of multiple go modules in go-pls (with a confusing error message to add to the confusion). For more information see here: https://github.com/golang/tools/blob/master/gopls/doc/workspace.md, but TLDR you should be able to fix this by adding a
Do you have the same issue in VSCode? If not I think we need to figure out how they work around this and copy that. |
Thanks for jumping in here to help @ConradIrwin - appreciate it! |
@ConradIrwin
|
@vxxvvxxv what do you get when you run In my case, I see the
Do you also have that? If so, what's the output when you run it with
|
Also interesting to know the version it fails on — we did release a new binary yesterday, that included a fix for #7534 with the exact same error. |
@mrnugget I got this:
@SomeoneToIgnore Zed notified me about auto-update, and after restarting, I have a new version ( I also tried downloading the latest release from GitHub, dragged Zed to Applications, opened it, and got the same thing. Logs from Zed:
|
This is very weird: just did So it looks like we have the logic for checking go releases right but it does not work for you due to either some local network issues (doubtfully, since you're able to post here) or some GitHub rate limiting mechanism? Unfortunately, that If not, then I could only suggest to wait a bit and try later: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28 states that it allows 60 requests/hour for unauthenticated users. |
Thinking of it more, it is not actually a network error at this point? @vxxvvxxv |
I just deleted the gopls directory and Zed downloaded it again, which looks correct. Unfortunately, I haven't seen any internet problems, nor do I think I'm catching Rate Limit (~5000 rps) from GitHub. @SomeoneToIgnore |
Part of #4471 (comment) Improves gopls error logging to actually see what is wrong with the output we failed to match against the version regex. Release Notes: - N/A
Thank you for trying all that. Great timing, please do a Apparently, that |
Thank you, yes I did before running I followed all the steps that are described here:
|
I think we could be onto something that breaks the gopls installation for you. Glad to continue debugging after you deal with that one. |
Alternative track to try, if zed/crates/zed/src/languages/go.rs Lines 119 to 137 in f3bfa11
It should be more or less clear what it does from that piece, so you can try repro the CLI commands locally and see what is not right with |
Thank you! Yeah, that's what it's all about. I suppose it would be useful to add the Troubleshooting section.
The code seems correct. I am waiting to finish downloading dependencies for the Also, I tried to run your command into bash and got this:
But if I try to run my locally gopls:
Also, I tried to run the downloaded
I'll post after I wait for the |
I ran into this issue the other day, The issue is that the binary is not signed when compiled using this toolchain. Unsigned binaries are killed immediately on launch, which is the behavior we see here. I would try signing the Zed installed binary manually (see here). |
I'm going to close this, since a lot has changed with our |
I am still having issues with Zed and Gopls. |
@pedronasser Can you create a new ticket and provide some debugging information? |
I'm having this issue too. Not sure where to find debugging info, nothing shows in the log as far as I can tell |
You can also provide debugging information: what's the project setup? Do you use GOPATH? go.mod? Is it a monorepo? Did you try |
I'm using go modules, I have a go.mod file. Its not a monorepo, go.mod/go.sum are in the project root. I do not have a |
Use |
thanks @mrnugget I needed to I found the error message in the logs. I had looked previously but must have missed it, tailing the log while it booted helped, rather than using |
Yeah that's a good point. Can you create a ticket with the relevant parts of the logs (meaning: shows where and why it failed) for this? |
Yeah, that error comes from |
not working for me either Golang is defunct with Zed. |
Hey @algoflows! I can't do much with that analysis. Can you create a ticket with details on your setup, log output, etc., anything? |
Check for existing issues
Describe the feature
Opened this project in Zed: https://github.com/nikitavoloboev/sol-pay
Opened this file: https://github.com/nikitavoloboev/sol-pay/blob/main/main.go
In Zed:
In VSCode:
No idea what I am doing wrong. But I wish I could use Zed for Go code too.
The text was updated successfully, but these errors were encountered: