1.8 KiB
Captured response
Found it: downstream c07e3cbd (“Preserve exact piker logger namespaces”) removes this assertion and the equivalent ones in data, broker and EMS startup. It also fixes the logger prefix handling.
That compatibility patch was present in our earlier evaluation stack but is absent from this base. I’ll apply its code and existing regression tests here as an unstaged patch.
Patch provenance
The five production-file changes and tests/test_logging.py reproduce the code/test changes from c07e3cbde2. This is a working-tree transplant, not a new commit or cherry-pick. The test file’s Git blob is 437554461d, matching the original commit. piker/log.py matches that commit.
Verification output
Logger tests with –noconftest: 4 passed in 0.36s. Normal pytest startup failed before collection because both Piker and modern Tractor register –ll. The logger tests use no project fixtures. An external disposable-registrar smoke script exercised open_pikerd(), maybe_spawn_datad(‘kraken’), registration and teardown successfully: Data daemon startup: OK
Follow-up response
Yep—the traceback shows the window’s closeEvent() explicitly sending SIGINT to its own process, which raises KeyboardInterrupt. Continuing a post-mortem REPL lets the original assertion unwind; it doesn’t resume successful startup. The resulting window close then adds that KBI. It’s secondary shutdown behaviour, and it makes the original failure harder to read.