Skip to content

Add CompilerMessage warning to groupBy and groupByAsync for parallel … #94

Add CompilerMessage warning to groupBy and groupByAsync for parallel …

Add CompilerMessage warning to groupBy and groupByAsync for parallel … #94

Triggered via push February 22, 2026 13:58
Status Success
Total duration 1m 14s
Artifacts

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build
The 'PackageIconUrl'/'iconUrl' element is deprecated. Consider using the 'PackageIcon'/'icon' element instead. Learn more at https://aka.ms/deprecateIconUrl
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L1842
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L1833
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2020
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2020
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.