brainy-smartphone-52410
06/06/2025, 1:08 PMlimited-student-10747
06/06/2025, 1:27 PMbrainy-smartphone-52410
06/06/2025, 1:46 PMWe're still getting the same error. Let's try one more approach. Let's look at the Lightstreamer documentation to see if there are any other requirements for the subscription request.
MCP Tool Result: tavily_tavily-search
Let's look at the WebSocket protocol implementation in our code:
Read wsok.rs
Let's look at the create_session message:
Read create_session.rs
Let's look at the Request macro implementation:
Read lib.rs
Let's look at the implementation of the Message trait:
Read mod.rs
Let's look at the implementation of the bind_session message:
Read bind_session.rs
Based on my investigation, I believe the issue might be related to the line endings in the subscription request. Let's modify the subscription.rs file to use "\r\n" instead of just "\n" for the control prefix:
Edited subscription.rs
Now let's build the project again:
Ran source "$HOME/.cargo/env" && cd /workspace/mongoose/monolith && cargo build -p l...
Let's run the ls_test application to see if our changes fixed the issue:
Ran source "$HOME/.cargo/env" && cd /workspace/mongoose/monolith && ...
Ran C-c
I've successfully fixed the issue with the Lightstreamer subscription request that was causing the server to send a close frame with the error "Cannot continue due to an unexpected error".
limited-student-10747
06/06/2025, 2:31 PMchilly-france-44439
06/06/2025, 2:45 PMbrainy-smartphone-52410
06/06/2025, 7:46 PM