Unreachable-server error drops the underlying exception text: "Could not reach Eco server: " with nothing after the colon #228

New issue

Closed

opened 2026-08-12 23:14:35 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 23:14:35 +00:00

Member

QA sweep, 2026-08-12.

Observed

get_server_status(server="eco.bleedcraft.com:3001") — a host from our own list_public_servers catalogue — returns:

{"view":"error",
 "message":"Could not reach Eco server: ",
 "error":"Could not reach Eco server: "}

The string is built to append the cause and then appends nothing. There is no timeout / DNS / connection-refused / HTTP status distinction, so there is nothing to act on: is the server down, is the port wrong, are we being blocked, did we time out?

Not a routing bug

The server parameter itself works. get_server_status(server="eco.greenleafserver.com:3021") on the same run returned full status for GreenLeaf Prime (403 total players, 12 laws, Eco 0.13.0.4). So this is purely message construction.

Expected

Include the exception type and detail, and the effective URL that was attempted. Something like:

Could not reach Eco server at http://eco.bleedcraft.com:3001/info: ConnectTimeout after 5s

QA sweep, 2026-08-12. ## Observed `get_server_status(server="eco.bleedcraft.com:3001")` — a host from our own `list_public_servers` catalogue — returns: ```json {"view":"error", "message":"Could not reach Eco server: ", "error":"Could not reach Eco server: "} ``` The string is built to append the cause and then appends nothing. There is no timeout / DNS / connection-refused / HTTP status distinction, so there is nothing to act on: is the server down, is the port wrong, are we being blocked, did we time out? ## Not a routing bug The `server` parameter itself works. `get_server_status(server="eco.greenleafserver.com:3021")` on the same run returned full status for GreenLeaf Prime (403 total players, 12 laws, Eco 0.13.0.4). So this is purely message construction. ## Expected Include the exception type and detail, and the effective URL that was attempted. Something like: ``` Could not reach Eco server at http://eco.bleedcraft.com:3001/info: ConnectTimeout after 5s ```

coilyco-ops referenced this issue

2026-08-12 23:34:54 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:36:09 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:47:23 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue from a commit

2026-08-13 04:27:10 +00:00

fix(errors): name the cause and URL on every unreachable-upstream error