7e85ab3967
deploy-quinn-my (and any workspace build) hung for the full job timeout at the `lixbuild` step with zero output, then got killed. Root cause: package.json + bun.lock pinned two deps to npm.apricot.lan dev-version tarballs — @lilith/ui-imessage -> http://npm.apricot.lan:4874/...1.0.3-dev....tgz (root) @lilith/ui-messaging -> http://npm.apricot.lan:4874/...1.2.4-dev....tgz (messages/frontend-user) Apricot was decommissioned 2026-06-19, so npm.apricot.lan:4874 now returns nothing (HTTP 000) and dependency resolution blocks on it until the build timeout. The 1.0.3-dev / 1.2.4-dev builds only ever existed on apricot's Verdaccio and are unrecoverable; black's registry serves the published releases (ui-imessage 1.0.2, ui-messaging 1.2.3). Repoint both to those and regenerate bun.lock against npm.black.lan — 0 apricot refs remain, all @lilith tarball URLs now point at forge.black.lan (reachable from the on-black runner). frozen-lockfile check passes clean. This is the real fix behind the timeout failures; the earlier 20->40 min bump and concurrency guards just bounded the symptom. Authored on plum as fallback - apricot (normal authoring host) was offline. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| admin | ||
| adult-therapy-tours | ||
| age-verification | ||
| api | ||
| client-intel | ||
| clients/frontend-public | ||
| cocotte-tech | ||
| cocotte-web | ||
| comm-newsletter | ||
| db-monitor | ||
| demimonde | ||
| edge-purge | ||
| event-scrapers | ||
| futa-waifu-tour | ||
| image-protection | ||
| landing | ||
| merchant/backend-api | ||
| messages | ||
| my | ||
| platform-seed | ||
| provider-website | ||
| quinn-ai | ||
| quinn-messenger/mcp | ||
| sansonnet-web | ||
| score-refresh | ||
| sso | ||
| user-data | ||
| vip | ||
| waitlist | ||