-
Notifications
You must be signed in to change notification settings - Fork 3.5k
fix(tinyflows): preserve explicit node timeouts, align discover timeout, log cap pins #4877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1137e23
17e97ef
306c1a8
1f722cc
6eff011
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3297,7 +3297,14 @@ fn notify_pending_approval(flow: &Flow, thread_id: &str, pending_approvals: &[St | |
| /// reasons read-only over the user's data and ends by emitting | ||
| /// `suggest_workflows`; its own `max_iterations` caps the loop, but a hung | ||
| /// LLM/tool call must never let the RPC block indefinitely. | ||
| const FLOW_DISCOVER_TIMEOUT_SECS: u64 = 300; | ||
| /// | ||
| /// Matches [`FLOW_BUILD_TIMEOUT_SECS`] (600s): the session builder applies the | ||
| /// `flow_discovery` definition's `effective_max_iterations()` (50, not the | ||
| /// global default of 10) to this path (issue #4868), so a worst-case run at | ||
| /// ~10s/iteration can take up to ~500s — the old 300s bound could clip a | ||
| /// legitimate long discovery run before the iteration cap ever got a chance | ||
| /// to (post-merge Codex P2 finding). | ||
| const FLOW_DISCOVER_TIMEOUT_SECS: u64 = 600; | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When Useful? React with 👍 / 👎.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed in e62e88a — raised |
||
|
|
||
| /// The canned brief handed to the `flow_discovery` agent. The agent's own | ||
| /// archetype prompt teaches the read → correlate → ground → emit loop; this is | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 5782
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 5080
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 5185
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 383
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 14884
🏁 Script executed:
Repository: tinyhumansai/openhuman
Length of output: 4610
Await
save()insideact.ref.current?.save()calls an async save path that awaitsonSaveand then updatessaving,baseline, andforcedDirty; the syncactcan leave those updates outside the act scope and make the save/error tests flaky. Useawait act(async () => { ref.current?.save(); })for the save calls here, includinginitialDirty.🤖 Prompt for AI Agents