[Repo Assist] Design parity with TaskSeq, batch 3 (#277) #176
Annotations
3 errors and 3 warnings
|
build
Process completed with exit code 1.
|
|
build:
src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2091
Duplicate definition of value 'skip'
|
|
build:
src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2091
Duplicate definition of value 'skip'
|
|
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/[email protected], actions/[email protected]. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build:
src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2651
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#L2651
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.
|