Skip to content

fix(summaries): drop wrong-page summaries; retry a stuck c0mpute node (0.26.1) - #129

Merged
sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
fix/summaries-crosstalk-retry
Nov 2, 2026
Merged

sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
fix/summaries-crosstalk-retry

Conversation

@sh1pt-actions-fleet

Copy link
Copy Markdown
Contributor

Anthony: "summarizing is failing right now" (on pit.world/search?q=saas).

What was wrong

  1. Same summary for different results. Three results summarized at once (Wikipedia, Salesforce, nichedb) all came back with one summary. The TronBrowser relay handed concurrent reads each other's page: one Obscura tab, navigate then read, interleaved. That is fixed at the source in fix(automate): concurrent fetch_page calls returned another call's page profullstack/tronbrowser.dev#176. Here, summaries written since 2026-11-02 11:00 UTC, when pages started being read through the relay, are dropped once at startup and rewritten on the next request.
  2. "The summarizer did not answer". Infernet answers 503 No live node serves "qwen2.5:7b", so jobs fell to any node. One node (dev-vienna) took a job and never answered, which used up the whole 90 s.
    • On the 503, pit.world now asks for the best general model Infernet lists as live (FALLBACK_MODELS, never a fine-tune or an abliterated model), then any node.
    • The first node gets about 55% of the budget, then there is one retry on another node. Refused keys (4xx) are not retried.

Tests

bun test: 413 pass, 0 fail. tsc is clean. New tests cover:

  • the model pick
  • the 503 → listed model → any node chain
  • a stuck node retried once, in under 6 s
  • a 401 not retried
  • the one-time cleanup drops only rows in the window and survives a restart

🤖 Generated with Claude Code

…te node (0.26.1)

- The TronBrowser relay handed concurrent reads each other's page (fixed in
  tronbrowser.dev #176), so different results got the same summary. Summaries
  written since 2026-11-02 11:00 UTC are dropped once and rewritten.
- 'No live node serves qwen2.5:7b' now falls to the best general model
  Infernet lists as live (never a fine-tune or abliterated one), then any
  node. A node that takes the job and never answers gets ~55% of the budget,
  then one retry on another node, instead of failing at 90 s.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sh1pt-actions-fleet
sh1pt-actions-fleet Bot merged commit ea6e100 into main Nov 2, 2026
4 checks passed
@sh1pt-actions-fleet
sh1pt-actions-fleet Bot deleted the fix/summaries-crosstalk-retry branch November 2, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant