Skip to content

[Repo Assist] Add CompilerMessage warning to groupBy/groupByAsync (closes #125) #113

[Repo Assist] Add CompilerMessage warning to groupBy/groupByAsync (closes #125)

[Repo Assist] Add CompilerMessage warning to groupBy/groupByAsync (closes #125) #113

Triggered via pull request February 22, 2026 13:56
Status Success
Total duration 1m 33s
Artifacts

pull-request.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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.