fix(examples): supervise example router URL needs /v1#400
Merged
Conversation
…ost 404s) The canonical supervise() example defaulted TANGLE_ROUTER_URL to https://router.tangle.tools — the chat endpoint lives under /v1, so the bare host returns a 404 HTML page, the supervisor brain gets an empty response, and the run silently ends no-winner. Default to .../v1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The canonical supervise() example defaulted the router URL to the bare host, which 404s (the chat endpoint is under /v1) → empty brain response → silent no-winner. Default to /v1.
Surfaced while empirically confirming #399 (the supervisor default prompt). Two deeper bugs found in that run, flagged for focused follow-up, NOT fixed here: (1) the supervisor loop silently swallows the brain's router error and degrades to no-winner —
routerChatWithToolsthrows on non-2xx, but the coordination driver catches it (violates no-silent-zeros); (2) no delivery even when workers spawn (the deliverable oracle isn't satisfied on a trivial task).