mirror of
https://gh-proxy.org/https://github.com/klinsmaya/multica.git
synced 2026-11-10 18:36:45 +08:00
79559ebb92
* test(wecom): move the relay claim tests off a shared Redis DB index (MUL-6890) The relay outcome tests keep their claims in Redis DB 12, which internal/service also takes for its own suite — and both flush that DB on entry and exit. `go test ./...` runs packages concurrently, so a flush from one package can delete a live delivery claim held by the other, and the publisher's outcome watch then reads an absent claim as "nobody delivered" and counts a drop for a reply the holder had already sent. That is the intermittent `outbound_dropped on the publisher = 1, want 0 — it was delivered` on main. Reproduced by running internal/service's Redis-backed tests alongside this one; fixed by giving the package an index nothing else uses, with the current allocation written down so the next one does not collide either. Co-authored-by: multica-agent <[email protected]> * build(turbo): generate fumadocs .source once instead of racing (MUL-6890) `build` and `typecheck` both ran `fumadocs-mdx` before their real work, and turbo is free to run those two tasks for the same package at the same time. fumadocs-mdx regenerates `.source/` by removing the directory and writing it back, so the two processes fight over one tree: whichever one mkdir's first can have it deleted underneath, and its write dies on `ENOENT: no such file or directory, open '.source/index.ts'` — the frontend-build failure on main, which is pure timing and passes on a rerun. Move the generation into its own `mdx` task that both depend on. It runs once, its output is cached like any other task's, and the two consumers can still run concurrently. Packages with no `mdx` script are unaffected: turbo skips a dependency nobody implements, the same way `cache-inputs` already works here. Co-authored-by: multica-agent <[email protected]> --------- Co-authored-by: J <[email protected]> Co-authored-by: multica-agent <[email protected]>