ClientHttp2Stream.h2StreamError from extension in code-server

Start by reproducing the RunMe AI Auto Cell request with the listed code-server, macOS, and extension versions, then inspect the ClientHttp2Stream.h2StreamError stack in the referenced bundled extension.js. Compare the failing code-server behavior with native VS Code and verify completion generation and insertion into a RunMe notebook cell as the done condition.

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome
• Local OS: MacOS
• Remote OS: MacOs
• Remote Architecture: Arm
• code-server --version:
  4.92.2 de65bfc9477f61bc22d0b1a23085d1f18bb25202 with Code 1.92.2

Steps to Reproduce

1. Run code-server
2. To install the RunMe VSCode Extension
3. Download and configure Foyle (www.foyle.io)
4. Run foyle serve
5. In RunMe enable AI Auto Cell Option
6. Open a markdown document as a RunMe notebook
7. Start typing in a markdown cell to trigger an RPC to Foyle

Expected

Foyle should generate a completion and insert it a cell into the notebook.

Actual

We get an error in vscode.

In the RunMe Output window we see the error

[2024-09-05T15:02:20.696Z] ERROR Runme(AIGenerate): AI Generate request failed ConnectError: [internal] Protocol error

Chrome console shows the following error

[Extension Host] Error in PromiseIterator: ConnectError: [internal] Protocol error
	at ConnectError.from (/home/user/.local/share/code-server/extensions/stateful.runme-3.7.2-jlewi.4/out/extension.js:1303796:20)
	at connectErrorFromNodeReason (/home/user/.local/share/code-server/extensions/stateful.runme-3.7.2-jlewi.4/out/extension.js:1302558:39)
	at Promise.reject (/home/user/.local/share/code-server/extensions/stateful.runme-3.7.2-jlewi.4/out/extension.js:1303074:110)
	at ClientHttp2Stream.h2StreamError (/home/user/.local/share/code-server/extensions/stateful.runme-3.7.2-jlewi.4/out/extension.js:1302963:22)
	at ClientHttp2Stream.emit (node:events:518:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

I believe the error indicates there is lack of support for HTTP2 clients. It works in native vscode so I suspect the problem must be something with code-server.

Logs

No response

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

No response