-
Notifications
You must be signed in to change notification settings - Fork 1.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 devfile LS Not working without updating Go language server plugin to the experimental version. #16113
Comments
@ScrewTSW how this affects UX with Go, other than warning? |
It is interesting to check Go LS features if they still work. |
Strange thing is that it's a one-time thing per deployment. I will try to reinstall che again and capture a screenshot of the message. |
Setting P1 after discussion with Tibor, looks like Go devfile is broken atm |
|
I thought a solution to this might be setting the che go plugin preference |
From my experience with this plugin on the vscode side, Which analysis tools are missing? They should be added to the go sidecar, since |
@amisevsk I think it was refering to |
@ScrewTSW Either way, I'm +1 on adding |
I just tried on che.openshift.io and it looks like the problem is that it's missing If I start a workspace and remove that preference the Edit: It looks like golangci-lint and gopls are both installed in the dockerfile: https://github.com/che-dockerfiles/che-sidecar-go/blob/1.12.9/Dockerfile#L72 |
|
Hi guys, is there any progress on that issue? This issue is still present in 7.10.0-SNAPSHOT. |
Can somebody describe what to do if notifications with update suggestions missed? |
The notification appears with every workspace startup until the plugin is updated. |
@ScrewTSW Could you please describe steps for updating LS if update suggestions missed? |
The fix for this issue would be to add it to the che-sidecar-go image ( If you miss the prompt, nothing bad happens (provided all the regular tools are installed), but it will return if you try to work on a project that uses go modules. |
@amisevsk But the title of this issue "Go devfile Not working without updating Go language server to the experimental version." and according to this I suppose if you missed notification the Go language server will not work. Am I right? |
fixed the issue name |
@rhopp found out that the problem, and why after update the LS works across the same workspace type after deletion/restarts is that what fixes the language server is a simple user preference setting:
After setting that preference the golang devfile LS works correctly |
So this is what's required to fix this issue, just the one setting? Or updating the Go LS plugin also needs to happen? |
I've created a new user, opened swagger and pushed
to the preferences endpoint and then tried to open a new golang devfile. the fix seems to be working even on newly created users that haven't been touched previously. |
Fixes issue where Che will complaing about the Go LS not being up to date. See eclipse-che/che#16113 Signed-off-by: Eric Williams <ericwill@redhat.com>
I believe the work here is done. |
But the error highlighting isn't working yet. (Info from Tibor Dancs) |
Describe the bug
Go devfile is showing notification about updating the version of Go vsix plugin and a warning regarding development tools missing in the path installation.
Che version
7.9.0-SNAPSHOT
Steps to reproduce
Expected behavior
No errors/warnings are present
Runtime
kubectl version
)oc version
) 4.3, 4.2minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
-a operator -p openshift --ssl --self-signed-cert
Environment
The text was updated successfully, but these errors were encountered: