mirror of
https://github.com/openclaw/openclaw.git
synced 2026-10-03 09:39:25 +00:00
14233c0e6d
* test(gateway): await yielded orchestrator cleanup Wait for the existing registry cleanup publication instead of racing real SQLite worker completion against a two-second polling window. Reuse the plugin-subagent observer and bind the new waits to the test abort signal so timeouts release their subscriptions. Keep yielded follow-up dispatch on real timers so the acknowledgement helper cannot prematurely run the registry sweeper against mocked run liveness. Preserve all requester lineage, announcement, delivery, cleanup, and predecessor lifecycle assertions. (cherry picked from commit 0591abe71e703b7cf7c69a42cd8b93287d9fe8d9) * fix(test): stop resume registry sweeper before gateway teardown The resume Gateway fixture left its subagent registry sweeper scheduled across files. A later tick used the retired module generation to open a shared-state worker against the next fixture's state directory. The worker registered with the old database lifecycle, escaped current teardown, and rejected the recreated SQLite pathname. Reset the fixture-owned registry without persistence before closing the Gateway so its timers stop before database retirement. Validation: the six-file same-worker driver reproduced the pathname error before the fix (270.19s instrumented), then passed all 49 tests (215.72s). The delete-state-lifecycle file passed all 10 tests alone (102.65s wall). Targeted oxfmt, oxlint, git diff --check, and independent review passed. All diagnostic instrumentation was removed. (cherry picked from commit 613b3f8818d21d0c0d65333b29aabce11dd5afe9) * test: settle reply recovery before deleting fixtures The aborted-restart fixture could delete its store while asynchronous main-session recovery-owner release was still preparing a write. Tracing reproduced that release recreating/registering the prior store during the following onAdopted test, invalidating the shared registry generation. Join reply successor-admission barriers and close each fixture database root before deleting its directory or resetting the reply registry. Extract the fixture owner to keep the existing large test file from growing. Re-enable the adopted-claim cancellation test. Production registry guards and retry contracts are unchanged. Validation with OPENCLAW_E2E_SKIP_BUILD=1 pnpm test:e2e:gateway against src/auto-reply/reply/agent-runner.runreplyagent.e2e.test.ts: - Original file: 220 passed, 1 registry failure, 1 skipped; 358.38s Vitest. - Original isolated adoption case repeated 20 times: passed; 170.95s Vitest. - Repaired aborted-restart/cancellation/adoption sequence: 3 clean runs, 3 tests each; CLI wall 225.68s, 190.48s, 99.70s. - Repaired full file: 221 passed, 1 different steering timeout; 528.47s Vitest. Remaining failure: keeps the replacement source when retired admission completes, first source admission did not persist (existing 5s guard). Focused replay passed in 151.18s Vitest; this does not establish a fix for that timeout. No timeout was changed. - Source test types, scoped oxlint, formatting, and independent review passed. Broad check:changed guards passed through the core graph boundary; stopped before its duplicate messaging type pass. pnpm tsgo:test:src passed that graph plus the remaining source test graphs. The full original CI shard and Telegram case were not replayed within the requested 35-minute investigation limit. (cherry picked from commit |
||
|---|---|---|
| .. | ||
| assets | ||
| api.ts | ||
| index.test.ts | ||
| index.ts | ||
| live.test.ts | ||
| models.ts | ||
| openclaw.plugin.json | ||
| package.json | ||
| provider-discovery.ts | ||
| README.md | ||
| tsconfig.json | ||
| video-generation-provider.test.ts | ||
| video-generation-provider.ts | ||
OpenClaw BytePlus Provider
Official OpenClaw provider plugin for BytePlus model inference and Seedance video generation.
Install from OpenClaw:
openclaw plugins install @openclaw/byteplus-provider
openclaw gateway restart
Set BYTEPLUS_API_KEY, then select a byteplus/* or byteplus-plan/* model.
See https://docs.openclaw.ai/concepts/model-providers#byteplus-international for model setup and https://docs.openclaw.ai/tools/video-generation for Seedance video generation.