question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to handle client message

See original GitHub issue
  • code-server version: latest git repo
  • OS Version: Linux VM

Description

I’ve tried building the latest code into it’s own image (docker build --rm --pull -t "codercom/code-server:beta" -f "Dockerfile" .) so that I can test the latest changes (and also wanted to build a C# specific version of code-server, with dotnet etc). But when I try running the image I get the following error and am unable to use it:

ERROR Failed to handle client message {“length”:2,“exception”:{“message”:“unknown message type”,“stack”:“Error: unknown message type\n at t.Server.handleMessage (/src/packages/server/out/cli.js:340:104610)\n at e.onMessage (/src/packages/server/out/cli.js:340:102979)\n at b.t.addEventListener.t (/src/packages/server/out/cli.js:340:101131)\n at b.n (/src/packages/server/out/cli.js:504:28094)\n at emitOne (events.js:116:13)\n at b.emit (events.js:211:7)\n at e.exports.T (/src/packages/server/out/cli.js:259:11285)\n at emitOne (events.js:116:13)\n at e.exports.emit (events.js:211:7)\n at e.exports.dataMessage (/src/packages/server/out/cli.js:259:19691)\n at e.exports.getData (/src/packages/server/out/cli.js:259:18932)\n at e.exports.startLoop (/src/packages/server/out/cli.js:259:16321)\n at e.exports._write (/src/packages/server/out/cli.js:259:15703)\n at doWrite (_stream_writable.js:396:12)\n at writeOrBuffer (_stream_writable.js:382:5)\n at e.exports.Writable.write (_stream_writable.js:290:11)\n at Socket.P (/src/packages/server/out/cli.js:259:11815)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at addChunk (_stream_readable.js:263:12)\n at readableAddChunk (_stream_readable.js:250:11)\n at Socket.Readable.push (_stream_readable.js:208:10)\n at TCP.onread (net.js:601:20)”}}

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
vimotacommented, Mar 27, 2019

Oh it does look like clearing the cache (or some other magic) made it work although I had tried that several times. I think I needed to close all existing sessions AND delete the cache.

0reactions
vimotacommented, Mar 28, 2019

Thanks for the help!

Read more comments on GitHub >

github_iconTop Results From Across the Web

RabbitMQ - what to do if client is unable to handle the message
Best practice is to put it on an error queue where it could be handled manually. Share.
Read more >
Error Messages: Examples, Best Practices & Common Mistakes
Useful error messages can keep users on your site and increase conversions. See examples and learn the best practices.
Read more >
PSMIN136W An error occurred while handling the messaging ...
PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request.
Read more >
A client can provide a failure message if fail to handle task #152
AT: a client can provide a failure message when a task is marked as failed; the failure message is automatically attached when the...
Read more >
Client side error handling techniques | zsiegel.com
A look into some techniques for client side error handling that have made my apps more robust and resilient when things go wrong....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found