35917681142
86%
main: 86%

Ran 23 Sep 2026 08:42PM UTC

Jobs 1

Files 5

Run time 1min

Badge

Embed ▾

Committed 23 Sep 2026 08:35PM UTC coverage: 85.915%. Remained the same

Build # 35917681142

Build Type

push

github

Committed by

web-flow

Commit Message

Document thread-safety and fork behavior (#10)

Coheriq guards its domain registry, domains, and engines with locks, but
nothing stated what callers may assume about threads or fork().  Add a
Design FAQ entry under the activation contract covering it.

The two properties worth knowing are that locks are held only for brief,
non-blocking setup bookkeeping, and that steady-state dispatch takes no
lock at all because each marked callable caches its resolved
implementation.  Forking after activation is supported and is the
expected worker pattern, since activation is process-global and one-way.
Forking concurrently with setup from another thread is not supported: a
lock held at the moment of the fork stays held in the child.

Also records the alternatives that were considered and not implemented
(PID-aware locks, os.register_at_fork), including why the PID-check
variant is less attractive than it first appears -- its check-and-replace
step is itself unsynchronized.

Assisted-by: Claude Opus 5

Coverage Stats

183 of 213 relevant lines covered (85.92%)

0.86 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	35917681142.1	23 Sep 2026 08:42PM UTC	5	85.92	GitHub Action Run

Qiskit / coheriq / 35917681142
86%
main: 86%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 35917681142

Qiskit / coheriq / 35917681142 86% main: 86%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 35917681142

Qiskit / coheriq / 35917681142
86%
main: 86%

README BADGES
x