ci/Zotero Sync/zotero-sync failed (#1011 @ d98f6105) #718

New Issue

kert · 2026-09-11T04:16:30Z

kert commented

2026-09-11 04:16:30 +00:00

Workflow: Zotero Sync
Job: zotero-sync
Run: #1011
Commit: d98f6105
Ref: refs/heads/main
Step: 6

A step in this CI job failed. Check the workflow run logs for details.

**Workflow:** `Zotero Sync` **Job:** `zotero-sync` **Run:** `#1011` **Commit:** `d98f6105` **Ref:** `refs/heads/main` **Step:** `6` A step in this CI job failed. Check the workflow run logs for details.

kert added the ci label 2026-09-11 04:16:30 +00:00

kert commented

2026-09-11 18:57:29 +00:00

Root cause (job 3924 log, run #1011): the mail-sync step fails with 'No such option: --merge-dupes'. The workflow (generated from stack.toml) passes --merge-dupes to stack bib sync-zotero inside the api container, but the running api image is fhirworx/api:a03801fb (three weeks old) and predates that option (added with the dedupe work, #665). Every nightly since 2026-08-27 failed the same way, so no mail-ingested or FR-rule items have reached Zotero for two weeks. Fix: roll the api image (COMMIT_SHA in .env, docker compose build api && docker compose up -d api mail-poller — mail-poller shares the image), then dispatch the workflow once by hand. The stale duplicates #667–#683 and #704 close with this one when the next run is green.

kert referenced this issue from a commit

2026-09-11 20:20:52 +00:00

fix(pfs,cli): the CPT parser imports rex lazily so the stack CLI starts in the api image (no fsspec there) — the nightly Zotero sync and mail poller run inside it (refs #718)

kert commented

2026-09-11 20:29:40 +00:00

Resolved: Zotero Sync run #1025 (workflow_dispatch, 2026-09-11) succeeded after rolling the api image to f7c3134. Root cause was image drift: the workflow passes --merge-dupes (added 2026-08-26, #665) to stack bib sync-zotero inside the api container, whose image (a03801fb) predated it; the first re-roll then hit a second latent break (the CPT parser imported rex → fsspec at module level, absent from the cli extra) fixed in f7c3134 with a regression test. Closing the auto-filed duplicates; the deploy-rollout note now records that workflow-invoked CLI changes need the api image rolled.

Resolved: Zotero Sync run #1025 (workflow_dispatch, 2026-09-11) succeeded after rolling the api image to f7c3134. Root cause was image drift: the workflow passes --merge-dupes (added 2026-08-26, #665) to stack bib sync-zotero inside the api container, whose image (a03801fb) predated it; the first re-roll then hit a second latent break (the CPT parser imported rex → fsspec at module level, absent from the cli extra) fixed in f7c3134 with a regression test. Closing the auto-filed duplicates; the deploy-rollout note now records that workflow-invoked CLI changes need the api image rolled.

kert closed this issue

2026-09-11 20:29:40 +00:00

kert referenced this issue

2026-09-11 20:29:53 +00:00

ci/Zotero Sync/zotero-sync failed (#1021 @ 0cf878d4) #722

Sign in to join this conversation.