Repository navigation
Unreachable code in tower-lsp dependency
#446
This issue is going to suckSo when I tried to run Worse, not only do I enter I didn't want to make an issue for this because technically the error does arise from another crate, but I thought I'd ask here what to do considering the error could happen again. Moreover, this issue from the |
Replies: 1 comment
|
That panic came from tower-lsp 0.20 (ebkalderon/tower-lsp#413): it fired when the server sent a response after the client side of the connection had closed. We've migrated to the maintained |
That panic came from tower-lsp 0.20 (ebkalderon/tower-lsp#413): it fired when the server sent a response after the client side of the connection had closed. We've migrated to the maintained
tower-lsp-server(#877), where a failed send ends the stream instead of panicking, with a test for a client disconnecting mid-request. It's on main and ships with the next release after 0.28.2.