homelab/stack
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

ci/Zotero Sync/zotero-sync failed (#983 @ d016f707) #704

New Issue
Closed
opened 2026-09-10 04:16:22 +00:00 by kert · 1 comment
kert commented 2026-09-10 04:16:22 +00:00
Owner
Copy Link

Workflow: Zotero Sync
Job: zotero-sync
Run: #983
Commit: d016f707
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:** `#983` **Commit:** `d016f707` **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-10 04:16:22 +00:00
kert commented 2026-09-11 20:29:40 +00:00
Author
Owner
Copy Link

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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label ci
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#704
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?