Skip to content

Conversation

@merolish
Copy link
Contributor

Summary

  • handle websocket control frames in the JRPC loop instead of attempting to parse them as JSON-RPC messages
  • rely on soketto's automatic handling of Ping frames and ignore Pong acknowledgements rather than replying to Pong frames
  • keep the handler responsive by exiting cleanly when the socket closes

Testing

  • cargo check --locked

Codex Task

@vercel
Copy link

vercel bot commented Dec 23, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
api-reference Ready Ready Preview, Comment Dec 23, 2025 5:32pm
component-library Ready Ready Preview, Comment Dec 23, 2025 5:32pm
developer-hub Ready Ready Preview, Comment Dec 23, 2025 5:32pm
entropy-explorer Ready Ready Preview, Comment Dec 23, 2025 5:32pm
insights Ready Ready Preview, Comment Dec 23, 2025 5:32pm
proposals Ready Ready Preview, Comment Dec 23, 2025 5:32pm
staking Ready Ready Preview, Comment Dec 23, 2025 5:32pm

@merolish
Copy link
Contributor Author

After testing, I confirmed that even without this PR the client receives pong responses, so this may not be needed (although it's probably better practice).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants