David Gageot 84ca8bdb03 fix: start peer-dependent toolsets after their peers settle ...

The deferred aggregator's Start lists its source toolsets' tools, so the
concurrent fan-outs could race it against the very toolsets it depends
on, yielding a spurious warning and missing deferred tools on the first
turn. Mark such toolsets with tools.PeerDependent and start them in a
second wave in both ensureToolSetsAreStarted (via new concurrent.ForEach)
and emitToolsProgressively.

emitToolsProgressively also consumes start outcomes in configuration
order again instead of a barrier, so an early fast toolset is counted in
the sidebar while a slow later one is still starting.

2026-07-16 18:38:16 +02:00

..

buffer_test.go

test: add t.Parallel() to eligible tests

2026-06-29 13:39:47 +02:00

buffer.go

feat(concurrent): add thread-safe methods and improve snapshot isolation

2026-05-18 09:27:39 +02:00

map_test.go

test: add t.Parallel() to eligible tests

2026-06-29 13:39:47 +02:00

map.go

feat: add Clear method to concurrent.Map

2026-05-18 10:28:18 +02:00

mapslice_test.go

fix: start peer-dependent toolsets after their peers settle

2026-07-16 18:38:16 +02:00

mapslice.go

fix: start peer-dependent toolsets after their peers settle

2026-07-16 18:38:16 +02:00

slice_test.go

test: add t.Parallel() to eligible tests

2026-06-29 13:39:47 +02:00

slice.go

feat(concurrent): add thread-safe methods and improve snapshot isolation

2026-05-18 09:27:39 +02:00