Issues

[Feature] `ORSet.add` and the map `put`s accept a `proto` identity that no peer can decode, so the value is written locally and then silently never converges

enhancement

priority: medium

#1033

· pathosDev opened

on Aug 6, 2026

[Bug] The tell-throughput benchmark reports 100,000 ops for an iteration that handled 9,999, so the published headline figure is about 10x too high and measures the drop path

bug

priority: high

production-goal

#1027

· pathosDev opened

on Aug 6, 2026

[Bug] `ensureCoordinator` runs before `numShardsByType` is populated, so every ShardCoordinator is built with 64 shards whatever you configure and entities above that id never get a home

bug

priority: high

production-goal

#1026

· pathosDev opened

on Aug 6, 2026

[Docs] Both `ManualScheduler` samples call `scheduler.advance` before the actor has processed the preceding tell, so the flagship determinism examples fail with a probe timeout and the microtask explanation names the wrong queue

documentation

priority: medium

production-goal

#1025

· pathosDev opened

on Aug 6, 2026

[Feature] No reusable failing-journal or failing-snapshot-store double exists, so a throwing append inside `persistAll`, a snapshot write that fails after a successful append, and recovery over a gapped stream are all untested

enhancement

priority: high

production-goal

#1024

· pathosDev opened

on Aug 6, 2026

[Feature] `MultiNodeTransport` offers only a binary partition and delivers via `queueMicrotask`, so gossip convergence under packet loss, reordering, duplication or latency is structurally untestable

enhancement

priority: high

production-goal

#1023

· pathosDev opened

on Aug 6, 2026

[Test] Five test cases assert `expect(true).toBe(true)` in place of the behaviour their title names and `CircuitBreaker.test.ts` discards the thrown error at eight sites, so a wrong error type or a silent no-op passes

#1022

· pathosDev opened

on Aug 6, 2026

[Test] `COV_COLOR` is hardcoded and the test-badge denominator is pass plus fail, so the coverage badge can never go red and a quarantined run is indistinguishable from a full one

#1021

· pathosDev opened

on Aug 6, 2026

[Test] The #310 default-mailbox guard checks `droppedCount === 0` on a mailbox that received nothing, so changing the default to capacity 3 with drop-new leaves `MailboxVariants.test.ts` fully green

#1020

· pathosDev opened

on Aug 6, 2026

[Test] `AllForOneStrategy` is never spawned and the `withinTimeRangeMs` restart window is never crossed, so both branches can be neutralised in `ActorCell` with every supervision-related test file still green

#1019

· pathosDev opened

on Aug 6, 2026

[Test] `main` requires only the `test` context with strict false and `develop` has no branch protection at all, so integration, build, multi-runtime, package-health and examples gate nothing on the branch where work lands

#1018

· pathosDev opened

on Aug 6, 2026

[Test] The persistence replay-mutation fuzzer imports nothing from src and proves theorems about `Array.prototype.reduce`, so nine badge-counted cases execute zero lines of the 19,814-line persistence layer

#1017

· pathosDev opened

on Aug 6, 2026

Navigation Menu

All issues

[Feature] `ORSet.add` and the map `put`s accept a `proto` identity that no peer can decode, so the value is written locally and then silently never converges

[Bug] The tell-throughput benchmark reports 100,000 ops for an iteration that handled 9,999, so the published headline figure is about 10x too high and measures the drop path

[Bug] `ensureCoordinator` runs before `numShardsByType` is populated, so every ShardCoordinator is built with 64 shards whatever you configure and entities above that id never get a home

[Docs] Both `ManualScheduler` samples call `scheduler.advance` before the actor has processed the preceding tell, so the flagship determinism examples fail with a probe timeout and the microtask explanation names the wrong queue

[Feature] No reusable failing-journal or failing-snapshot-store double exists, so a throwing append inside `persistAll`, a snapshot write that fails after a successful append, and recovery over a gapped stream are all untested

[Feature] `MultiNodeTransport` offers only a binary partition and delivers via `queueMicrotask`, so gossip convergence under packet loss, reordering, duplication or latency is structurally untestable

[Test] Five test cases assert `expect(true).toBe(true)` in place of the behaviour their title names and `CircuitBreaker.test.ts` discards the thrown error at eight sites, so a wrong error type or a silent no-op passes

[Test] `COV_COLOR` is hardcoded and the test-badge denominator is pass plus fail, so the coverage badge can never go red and a quarantined run is indistinguishable from a full one

[Test] The #310 default-mailbox guard checks `droppedCount === 0` on a mailbox that received nothing, so changing the default to capacity 3 with drop-new leaves `MailboxVariants.test.ts` fully green

[Test] `AllForOneStrategy` is never spawned and the `withinTimeRangeMs` restart window is never crossed, so both branches can be neutralised in `ActorCell` with every supervision-related test file still green

[Test] `main` requires only the `test` context with strict false and `develop` has no branch protection at all, so integration, build, multi-runtime, package-health and examples gate nothing on the branch where work lands

[Test] The persistence replay-mutation fuzzer imports nothing from src and proves theorems about `Array.prototype.reduce`, so nine badge-counted cases execute zero lines of the 19,814-line persistence layer

Search results