company: backend company-capf fails with json unmarshal error. #4281
Replies: 3 comments
-
Collect the data as described when you start a bug report. |
Beta Was this translation helpful? Give feedback.
-
I am not exactly sure if this is a bug or something wrong with my configuration, hence started it as a discussion. The issue i suspect is that module lookup is not happening. I assume that's what is happening and as a result of it , i suspect the above is happening. I have check other issues around this and it was mentioned that it could happen because of networking issue, I tried checking if the container can access the network and that seems to work fine. The setup here, The workspace directory where my go source exists is mounted on to container as (read only). I made sure that it's mounted with similar directory tree on the container. I am suspecting, i am missing something very basic here. This is first time i am trying this kind of setup. |
Beta Was this translation helpful? Give feedback.
-
closing this discussion as the issue got resolved , the issue was that the project directory mounted on container had permission issues. Once the permissions were fixed , issue was resolved. |
Beta Was this translation helpful? Give feedback.
-
I am using emacs with remote gopls server (Running inside a container) and configured lsp-mode on my emacs. When i open any go file and type "fmt. " the following error is displayed and doesn't show any functions of fmt.
Company: backend company-capf error "unmarshaling result: json: cannot unmarshal object into Go struct field CompletionItem.items.documentation of type string" with args (candidates )
My emacs configuration:
Any hints/ideas on how i could resolve the issue.
Beta Was this translation helpful? Give feedback.
All reactions