Co-pilot not working on server

[fedbont94]

Select Topic Area

Bug

Body

Hi all,

I have been using github copilot as a VsCode extension on my laptop and on 2 different clusters without any problems.
However, I have a problem/bug on a cluster. The problem is that github copilot is not working at all.
When I look at the output on VsCode, I see that:

VsCode output: GitHub Copilot
[ERROR] [promptlib proxy] [2023-01-26T10:18:03.103Z] {}
[ERROR] [promptlib proxy] [2023-01-26T10:18:03.107Z] {}

VsCode output: Windows
2023-01-26 11:18:03.111 [error] [Extension Host] [ERROR] [promptlib proxy] [2023-01-26T10:18:03.103Z] RangeError: WebAssembly.Memory(): could not allocate memory
at Object.r (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:67775)
at Object.87 (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:110658)
at n (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:110986)
at Object.306 (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:19565)
at n (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:110986)
at Object.563 (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:14830)
at n (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:110986)
at /path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:111040
at /path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:111324
at Object. (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/worker.js:1:111346)
2023-01-26 11:18:03.111 [error] [Extension Host] [ERROR] [promptlib proxy] [2023-01-26T10:18:03.107Z] Error: Worker thread exited with code 1.
at Worker. (/path/to/home/.vscode-server/extensions/github.copilot-1.70.8099/dist/extension.js:8:866289)
at Worker.emit (node:events:526:28)
at Worker.[kOnExit] (node:internal/worker:278:10)
at Worker..onexit (node:internal/worker:198:20)

I already contacted the server support and they gave me the following info, if they can help:

• The first error message "promptlib proxy" looks like a connection problem.
  There is no firewall or otherwise blocking of internet traffic from within ServerName to the outside.
  On the other side all incoming traffic to ServerName is blocked. The only accessible port is ssh
• The second error message "WebAssembly.Memory(): could not allocate memory" looks like the addon reached the memory limit on the login node.
  A single process is not allowed to use more than 8GB of memory

$ code --version
1.74.3
97dec172d3256f8ca4bfb2143f3f76b503ca0534
x64

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy

Can anyone help me with this? or has an idea on how to solve this?

Thanks a lot!

[jge162]

Hello @fedbont94 One way to potentially work around this issue would be to try and limit the amount of memory that the GitHub Copilot extension is using by adjusting its settings.

Also another option could be to try running the extension on a different cluster that has more available memory.

👍

[jge162]

Adjust the settings of VsCode, you can try to lower the amount of memory used by VsCode by adjusting the settings in the "settings.json" file. You can try adding this line in the settings: "editor.maxMemory": 250000000, find a value that works. That’s just a placeholder value. Like using pass in a Python function.

Also close Unnecessary tabs, u have open in vscode. Anything to reduce memory usage. Even possible if avail expand your computers memory.

[jge162]

If you do these things it will solve your issue with memory.

[jge162]

@fedbont94 ignore harranderjaki below. Seems to be a bot. Just joined GitHub 10 min ago.

[fedbont94]

Hi! Thanks again for the suggestion.
I fear it did not work. adding "editor.maxMemory": 250000000 does not have any effect. I tried different values but it did not change anything. I actually think that there is no such option editor.maxMemory since the it was not shown as a normal variable but as a unknown.

[srzvziihk21955]

I had the same problem.
I think the problem is that the remote machine is out of memory.

[AntonBogun]

Bump, since this is still an issue. What is interesting is that copilot does not have RangeError: WebAssembly.Memory(): could not allocate memory error in .sh, .json, .cpp, .rs (all I tried) files, but refuses to work in .py files.

[fedbont94]

Hi all!

I come back to this issue (which is still partially there).
I found a few ways around this problem. So if you have this issue you could follow these steps and hopefully it would work.

Solution 1. (easier in my opinion):
Copilot does not work if I am in the home folder. However if I open a subfolder (e.g. "code work/") which is a folder in my home directory, vs-code will open a new window. Sometimes copilot works in this workspace. (Don't ask me why, I have no idea).

Solution 2. (not practical):
You could start an interactive job. Instead of submitting a job, allocate some memory (e.g. on SLURM, "alloc ...") you may then want to restart your vscode with something like code tunnel or something similar and eventually that would work.
I do not like option 2 because it actually takes useful resources from the cluster. However, I hope any of this solution could help you to solve the issue.

P.S. I have a heavy home folder with many files, and sometimes also Pylance takes some time to start. I read it is because it somehow needs to map all files in the folder or something. Idk if copilot has the same problem.

Cheers all and happy coding

[hkchengrex]

I'm having the same error here. Opening a small folder (even with just one .py file) unfortunately does not help. I don't think the server is running out of memory either -- there are >400GB of free memory and I can easily occupy >10GB of memory with numpy running on the same login node.

[hkchengrex]

I find this solution works: https://qiita.com/bestvimmer_JP/items/2baa7d9f991cf92be99f

Adding the following to settings.json

    "remote.extensionKind": {
        "GitHub.copilot": ["ui"],
      }

I believe the underlying cause remains unsolved but this is a working temporary solution for me.

[Ming-Qin-tech]

it's not work for me

[YogiOnBioinformatics]

@hkchengrex You are a savior! I'm in a state of euphoria after this worked.

P.S. I'm also a PhD student as well. 😀

[YuyueminAustin]

thank you, seems the extension is buggy when depending on workspace, this solution works for me to set the extensions close to ui

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐