mirror of
https://github.com/hansjone/dsh-im-ops.git
synced 2026-10-11 05:23:18 +08:00
955c2217fd
A long-running Harness task was falsely reported as MODEL_REPLY_TIMEOUT after the fixed 10-minute deadline even though the backend was still working. Replace the hard wall-clock deadline with an activity-based stall window: the wait renews whenever the turn produces new events, the control ownership is active, or (mid-turn with no new events) Harness still reports the session as running. Only a genuine stall with no progress for the whole timeoutMs window fails fast. This is the shared harness-client layer, exercised end-to-end by the Feishu channel (which already exposes HARNESS_REPLY_TIMEOUT_MS); other channels inherit the same fix. Adds two regression tests: a long-running turn with periodic activity completes instead of timing out, and a genuinely stalled turn still fails with harness-reply-timeout. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| bridge.test.mjs | ||
| client-api.test.mjs | ||
| config.test.mjs | ||
| connection-supervisor.test.mjs | ||
| connection-test-client.test.mjs | ||
| feishu-app.test.mjs | ||
| feishu-cards.test.mjs | ||
| feishu-channel.test.mjs | ||
| feishu-proxy.test.mjs | ||
| feishu-runtime.test.mjs | ||
| group-message-permission-manager.test.mjs | ||
| harness-client.test.mjs | ||
| lark-sdk-handshake-patch.test.mjs | ||
| message-utils.test.mjs | ||
| multi-bot-controller.test.mjs | ||
| plugin-config-store.test.mjs | ||
| plugin-controller.test.mjs | ||
| plugin-host.test.mjs | ||
| registration-manager.test.mjs | ||
| repair-manager.test.mjs | ||
| slash-command-registry.test.mjs | ||
| state-store.test.mjs | ||