Repository navigation
Extend default memory pre-turn wait to five seconds - #7346
Conversation
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (3)
Comment |
Tiny Sweeper reviewTiny Sweeper reviewed this change across 6 lane(s) and found 1 active actionable finding(s). Detailed lane evidence and any incomplete work are listed below. State: Changes requested Review snapshot
Completeness: Complete What changedThe review could not produce a supported behavioral summary; inspect the cited changed surface and lane details below. FeaturesNone identified with supported citations. TestsNo supported feature-to-test mapping was produced. Test execution is not inferred. Findings
Pending checks: Rust E2E (mock backend), Build Playwright E2E Artifact, E2E (Playwright / web lane), Desktop E2E (full suite, 3 OS) Before merge
Agent review detailscritique
security
tests
commits
description
e2e
Evidence and run details
|
There was a problem hiding this comment.
Requesting changes: 1 lane(s) blocking, worst finding is high.
Fix or reply to the findings below and push. The next review clears this automatically once they are gone — you should not need to dismiss anything by hand.
Findings not posted inline
-
End-to-end job
Storage e2e on MongoDBwill not run on this change (.github/workflows/storage-mongodb.yml): e2e-not-triggeredStorage e2e on MongoDBin.github/workflows/storage-mongodb.ymlwill not run for this pull request: its workflow'spaths:filter matches nothing this pull request changed. The change is merged without its end-to-end suite having seen it.
$0.0039 · 68,625 in / 2,219 out · 9,787 cached (14%) · gpt-5.6-luna, glm-5.3-flash
critique: $0.0019 · 27,453 in / 689 out · 4,141 cached (15%) · gpt-5.6-luna
security: $0.0018 · 24,058 in / 518 out · 1,870 cached (8%) · gpt-5.6-luna
tests: $0.0000 · 4,528 in / 100 out · 64 cached (1%) · glm-5.3-flash
description: $0.0000 · 4,184 in / 54 out · 1,536 cached (37%) · glm-5.3-flash
e2e: $0.0000 · 5,425 in / 211 out · 2,048 cached (38%) · glm-5.3-flash
Summary
Increase OpenHuman's default memory pre-turn wait from 1,500 ms to 5,000 ms. Explicit
pre_turn_timeout_mssettings still take precedence. Update the configuration example and spec to match.The companion TinyMemory eval PR (tinyhumansai/tinymemory#254) mirrors this deadline. In a fresh 100-document live CortexDB run at 5 seconds, the lexical answer completed in 2.08 seconds and the paraphrase miss in 1.78 seconds, with no timeout. The paraphrase needs a separate retrieval-quality fix: its correct document ranked 23rd in a direct 100-event recall. Earlier 1.5-second scale runs often timed out, but these are different collections and do not establish a paired timeout-rate change.
Behavior and API
No public API change. The default wait is now 5 seconds; explicitly configured values are unaffected. A timed-out memory task still follows the existing background behavior.
Validation
default_pre_turn_waits_five_seconds_for_memoryfailed before the default change (1,500 versus 5,000).cargo fmt --all -- --check— passed.scripts/ci-cancel-aware.sh cargo test -p openhuman --lib default_pre_turn_waits_five_seconds_for_memory— compiling; result will be added when complete.Related: tinyhumansai/tinymemory#251