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

[nb] zotero_tutorial.py: ancestor-stopped: This cell wasn't run because an ancestor was stopped with mo.stop: #559

New Issue
Closed
opened 2026-07-10 14:32:56 +00:00 by kert · 1 comment
kert commented 2026-07-10 14:32:56 +00:00
Owner
Copy Link

Auto-filed by the notebook error filer (nb-sig:b63a3ce3fae2 — do not edit this marker; dedup and auto-close key on it).

  • Notebook: zotero_tutorial.py
  • Error: ancestor-stopped: This cell wasn't run because an ancestor was stopped with mo.stop:
  • Source: nb-integration/all
(no traceback captured)

This issue is closed automatically when the error stops occurring.

Auto-filed by the notebook error filer (`nb-sig:b63a3ce3fae2` — do not edit this marker; dedup and auto-close key on it). - **Notebook:** `zotero_tutorial.py` - **Error:** `ancestor-stopped`: This cell wasn't run because an ancestor was stopped with `mo.stop`: - **Source:** nb-integration/all ``` (no traceback captured) ``` This issue is closed automatically when the error stops occurring.
kert added the notebooks label 2026-07-10 14:32:56 +00:00
kert commented 2026-07-10 15:53:53 +00:00
Author
Owner
Copy Link

Cascade noise, not a distinct failure: marimo marks every descendant of a failed/stopped cell with its own error output ('An ancestor raised an exception' / 'ancestor-stopped'), and the filer treated each as a separate signature. Since cc094bd nb_integration.parse_snapshot drops cascades, so only the root-cause issue for this notebook stays open. This signature will not be reported again.

Cascade noise, not a distinct failure: marimo marks every descendant of a failed/stopped cell with its own error output ('An ancestor raised an exception' / 'ancestor-stopped'), and the filer treated each as a separate signature. Since cc094bd nb_integration.parse_snapshot drops cascades, so only the root-cause issue for this notebook stays open. This signature will not be reported again.
kert closed this issue 2026-07-10 15:53:53 +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 notebooks
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dom kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#559
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?