Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(mcp): recover when a live hyperd becomes unresponsive

Open
  • Is something wrong?
#242 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
api, backend

Research direction

Start at the release hyperdb-mcp daemon request handling and the existing REPORT_HYPERD_ERROR and rate-limited restart path. Trace how a live hyperd child handles the SELECT 1 reproduction, then add bounded failure detection without replaying mutating requests. Done means a clear timeout/error is returned, a later request reaches a replacement process, and an isolated cleanup-safe integration test covers the wedged live process.

Written by the indexing model from the issue text.

Description

Problem

The MCP daemon currently restarts its managed hyperd when the child exits, or after a client reports a connection-lost error. It does not recover a process that remains alive but stops serving requests.

Reproduction

  1. Start the release hyperdb-mcp daemon.
  2. Send SIGSTOP to its managed hyperd child.
  3. Invoke a harmless read-only MCP query such as SELECT 1.

Observed: the query remained blocked for more than 30 seconds; the daemon continued to see the child as alive (process state T) and did not restart it. The test client had to be interrupted.

Desired behavior

A wedged-but-live hyperd should be detected with bounded latency. The current request may return a clear timeout/error, but a later request should connect to a rate-limited replacement hyperd. Do not automatically replay a potentially mutating request.

Possible direction

Add a bounded query/connection timeout or an independent responsiveness probe that feeds the existing REPORT_HYPERD_ERROR and rate-limited restart path. Cover the live-but-unresponsive case with an isolated, cleanup-safe integration test.

Dominant language
Rust
Stars
2
Forks
2
Avg merge
12h 2m
Merged PRs (30d)
60

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tableau/hyper-api-rust

All issues in tableau/hyper-api-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.