-
Notifications
You must be signed in to change notification settings - Fork 18
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
lsp-server crashes on drakma http request #167
Comments
I'm able to recreate the issue, so that's a plus. When I run it, it's getting a socket error because of some non-blocking issue but then something is blowing up trying to send the debugger request. I see the message being sent in the lsp code, but not in the vscode trace, so I'm thinking something is causing the message to get formatted wrong. I'm still trying to figure out what's going on there. |
I was trying to duplicate this on Ubuntu Linux but it seems to be working for me:
I tested this with If I'm not testing this properly let me know and I'll try to get it fail. My original goal was to use my |
I now have a theory. It's not generating the headers correctly for the packet. For no good reason, it's not putting \r\n line endings, it's only putting \n. It's not doing that for anything else, only the debugger request for the drakma call. I'm going to switch how I generate the packets and see if I can get it to stop doing that. With any luck, that'll fix it. It's not too surprising that it might be working correctly on Linux. SBCL on Windows is known to be flaky. |
OK, that fixed it. It should go into the debugger now instead of crashing the server. |
Platform: Windows
being run causes Alive to report an error, with
as the only message in the output log. The same code runs fine through my sbcl instance in the vscode terminal.
The text was updated successfully, but these errors were encountered: