[repo-assist] Monthly Activity 2026-09

Aperta
#471 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
10/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
fsharp, github-actions
Ambito
tooling

Direzione di ricerca

Questa issue è un report mensile generato sull'attività dei maintainer, non una richiesta di modifica autonoma. Inizia esaminando le issue e le pull request collegate, in particolare #468, #470, #473, #463 e #442, insieme a TaskSeqInternal.fs e al README dove indicato. Non esiste un'unica condizione di completamento; le azioni di manutenzione elencate richiederebbero decisioni o implementazioni separate.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

automation enhancement repo-assist

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Activity for September 2026

Suggested Actions for Maintainer

Comprehensive list of all pending actions requiring maintainer attention:

  • Review PR #468: Dependabot bump of github/gh-aw-actions/setup 0.86.2→0.87.10 — View
  • Review PR: test: add SideEffects module to ReplicateInfinite and ThreadState test files — created this run
  • Apply manually: issue #463 contains a ready patch (Actions version bumps: checkout v7, setup-dotnet v6, cache v6, upload-artifact v7, dorny/test-reporter v3) that Repo Assist could not push directly because it touches protected .github/workflows/*.yaml files — a maintainer needs to download and apply it via the instructions in the issue — View
  • Apply manually: issue #442 contains a ready patch (bundled Dependabot Actions updates + SideEffects tests for FoldWhile/Do) blocked for the same protected-workflow-file reason — View
  • Investigate #452: Orleans-specific TaskSeq.map/for..yield final-item duplication bug. Root cause narrowed to shared CE/resumable-code machinery, but not reproducible offline — needs a maintainer/contributor with real Orleans dev access to drive further — View
  • Check comment on #62: tail recursion discussion — awaiting maintainer direction on whether to pursue stub overloads for TaskSeqBuilder now that upstream YieldFromFinal fix has landed — View
  • Triage #466: new feature request for a ValueTaskSeq type (ValueOption/ValueTask-based) from @xperiandri — unlabelled, needs feasibility assessment — View

Future Work for Repo Assist

  • Do NOT re-attempt: rev/sort, allPairs, zip4, map3, iteri2, splitInto, exists2, map2, findBack (all rejected/closed)
  • Do NOT re-engage on issue #139 (TaskEx index) or #62 (tail recursion) unless new human activity appears
  • Confirmed lengthBeforeMax, unfold, unfoldAsync, tryPick, tryFind, tryFindIndex in TaskSeqInternal.fs are early-exit patterns that cannot be converted to the while! idiom (no break in F#'s task/taskSeq CEs) — do not re-attempt this perf conversion
  • Test files still without a SideEffects module: TaskSeq.Empty.Tests.fs (has an inline side-effect test but no dedicated module — may not need one), TaskSeq.Let.Tests.fs (binding-focused, may not need one). ReplicateInfinite.Tests.fs and ThreadState.Tests.fs now have one, added this run.
  • Protected-file limitation: any engineering task touching .github/workflows/*.yaml cannot be pushed directly by the bot; results in a stranded issue with manual patch instead of a PR (see #463, #442)

Run History

2026-09-04 — Run
  • 🔧 Created PR: test: add SideEffects module to TaskSeq.ReplicateInfinite.Tests.fs and TaskSeq.ThreadState.Tests.fs (Task 9, substituted for Task 8 — no viable while! perf conversions remained after verifying the last few early-exit patterns) — build succeeds, full suite 4469 passed / 0 failed
  • 🔍 Verified no open issue is fixable under Task 3 criteria (no bug/help wanted/good first issue labelled issues); substituted with test-coverage work
  • 📁 Closed #465 (August 2026 monthly activity) and opened this issue for September

Generated by 🌈 Repo Assist, see workflow run.
Comment /repo-assist to run again

Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Activity for September 2026

Suggested Actions for Maintainer

Comprehensive list of all pending actions requiring maintainer attention:

  • Review PR #468: Dependabot bump of github/gh-aw-actions/setup 0.86.2→0.87.10 — View
  • Review PR: test: add SideEffects module to ReplicateInfinite and ThreadState test files — created 2026-09-04 — View
  • Review PR: docs: document known Debug-mode F# compiler bug affecting taskSeq (#473) — created this run
  • Apply manually: issue #463 contains a ready patch (Actions version bumps: checkout v7, setup-dotnet v6, cache v6, upload-artifact v7, dorny/test-reporter v3) that Repo Assist could not push directly because it touches protected .github/workflows/*.yaml files — a maintainer needs to download and apply it via the instructions in the issue — View
  • Apply manually: issue #442 contains a ready patch (bundled Dependabot Actions updates + SideEffects tests for FoldWhile/Do) blocked for the same protected-workflow-file reason — View
  • Investigate #452: Orleans-specific TaskSeq.map/for..yield final-item duplication bug. Root cause narrowed to shared CE/resumable-code machinery, but not reproducible offline — needs a maintainer/contributor with real Orleans dev access to drive further — View
  • Check comment on #62: tail recursion discussion — awaiting maintainer direction on whether to pursue stub overloads for TaskSeqBuilder now that upstream YieldFromFinal fix has landed — View
  • Triage #466: feature request for a ValueTaskSeq type (ValueOption/ValueTask-based) from @xperiandri — now labelled enhancement/feature request/needs triage; still needs a feasibility decision — View
  • Check comment on #473: root-caused a reported bug (taskSeq silently truncates in Debug builds on .NET SDK 10.0.400+) to an upstream F# compiler regression, dotnet/fsharp#20466, with a fix already in progress at dotnet/fsharp#20469 — recommend tracking the upstream PR for closure, no action needed in this repo — View
  • Track upstream: dotnet/fsharp#20469 (compiler fix for the Debug-mode state-machine lowering bug affecting taskSeq) — once merged and shipped in an SDK, #473 can be closed — View

Future Work for Repo Assist

  • Do NOT re-attempt: rev/sort, allPairs, zip4, map3, iteri2, splitInto, exists2, map2, findBack (all rejected/closed)
  • Do NOT re-engage on issue #139 (TaskEx index) or #62 (tail recursion) unless new human activity appears
  • Confirmed lengthBeforeMax, unfold, unfoldAsync, tryPick, tryFind, tryFindIndex in TaskSeqInternal.fs are early-exit patterns that cannot be converted to the while! idiom (no break in F#'s task/taskSeq CEs) — do not re-attempt this perf conversion
  • Test files still without a SideEffects module: TaskSeq.Empty.Tests.fs (has an inline side-effect test but no dedicated module — may not need one), TaskSeq.Let.Tests.fs (binding-focused, may not need one)
  • Protected-file limitation: any engineering task touching .github/workflows/*.yaml cannot be pushed directly by the bot; results in a stranded issue with manual patch instead of a PR (see #463, #442)
  • Watch dotnet/fsharp#20469 for merge/release; once shipped in an SDK, close out #473 with a comment confirming the fix and remove the "Known issues" note from README once the fixed SDK is broadly available

Run History

2026-09-11 13:45 UTC — Run
  • 🏷️ Labelled #473 with bug, compatibility, blocked: awaiting-fsharp-feature
  • 🏷️ Labelled #466 with enhancement, feature request, needs triage
  • 🏷️ Labelled #452 with bug, needs investigation, compatibility
  • 💬 Commented on #473: reproduced the reported Debug-mode taskSeq truncation locally, root-caused it to an upstream F# compiler regression (dotnet/fsharp#20466), and pointed to the in-progress fix (dotnet/fsharp#20469) plus a Release-build workaround
  • 🔧 Created PR: docs: document known Debug-mode F# compiler bug affecting taskSeq (#473) — README "Known issues" section + release-notes entry
2026-09-04 — Run
  • 🔧 Created PR: test: add SideEffects module to TaskSeq.ReplicateInfinite.Tests.fs and TaskSeq.ThreadState.Tests.fs (Task 9, substituted for Task 8 — no viable while! perf conversions remained after verifying the last few early-exit patterns) — build succeeds, full suite 4469 passed / 0 failed
  • 🔍 Verified no open issue is fixable under Task 3 criteria (no bug/help wanted/good first issue labelled issues); substituted with test-coverage work
  • 📁 Closed #465 (August 2026 monthly activity) and opened this issue for September

Generated by 🌈 Repo Assist, see workflow run.
Comment /repo-assist to run again> Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Activity for September 2026

Suggested Actions for Maintainer

Comprehensive list of all pending actions requiring maintainer attention:

  • Review PR #480: Dependabot bump of github/gh-aw-actions/setup 0.88.8→0.89.15 — Review
  • Review PR #470: test: add SideEffects module to ReplicateInfinite and ThreadState test files — Review
  • Review PR: docs: Known Issues section for Debug-mode compiler bug affecting taskSeq (#473) — created this run
  • Apply manually: issue #463 contains a ready patch (Actions version bumps) blocked by protected .github/workflows/*.yaml files — a maintainer needs to apply it manually per the issue's instructions — View
  • Apply manually: issue #442 contains a ready patch (bundled Dependabot Actions updates + SideEffects tests) blocked for the same protected-workflow-file reason — View
  • Check comment on #452: confirmed the newly-reported Debug-mode test failures (from @majocha) are the same upstream compiler regression as #473 (dotnet/fsharp#20466), not a new Orleans-specific bug — reproduced locally with SDK 10.0.400 in Debug. The original Orleans "duplicated final item" symptom remains open and still needs a maintainer/contributor with real Orleans access to progress — View
  • Check comment on #62: tail recursion discussion — awaiting maintainer direction on whether to pursue YieldFromFinal stub overloads now that the upstream compiler fix has landed — View
  • Triage #466: feature request for a ValueTaskSeq type (ValueOption/ValueTask-based) from @xperiandri — labelled enhancement/needs triage; still needs a feasibility decision — View
  • Track upstream: dotnet/fsharp#20469 (compiler fix for the Debug-mode state-machine lowering bug affecting taskSeq) — once merged and shipped in an SDK, #473 can be closed and the README "Known issues" note removed — View

Future Work for Repo Assist

  • Do NOT re-attempt: rev/sort, allPairs, zip4, map3, iteri2, splitInto, exists2, map2, findBack (all rejected/closed)
  • Do NOT re-engage on issue #139 (TaskEx index) or #62 (tail recursion) unless new human activity appears
  • Confirmed lengthBeforeMax, unfold, unfoldAsync, tryPick, tryFind, tryFindIndex in TaskSeqInternal.fs are early-exit patterns that cannot be converted to the while! idiom — do not re-attempt this perf conversion
  • Protected-file limitation: any engineering task touching .github/workflows/*.yaml cannot be pushed directly by the bot; results in a stranded issue with manual patch instead of a PR (see #463, #442)
  • Watch dotnet/fsharp#20469 for merge/release; once shipped in an SDK, close out #473 and #452's Debug-mode angle with a confirming comment, and remove the "Known issues" README note once the fixed SDK is broadly available
  • #452's original Orleans-specific duplication (distinct from the now-confirmed Debug/compiler-bug symptom) still needs a real Orleans repro environment to progress further

Run History

2026-09-18 13:46 UTC — Run
  • 🔧 Created PR: docs: add Known Issues section for Debug-mode compiler bug affecting taskSeq (#473) — the earlier attempt (issue #476) had been blocked by a false-positive protected-files check on README.md, which resolved cleanly this run
  • 💬 Commented on #476 noting the new PR supersedes the manual-patch instructions
  • 💬 Commented on #452: reproduced @majocha's Debug-mode test failure locally with SDK 10.0.400, confirmed it is the same upstream compiler regression as #473 (not a new Orleans-specific bug), and clarified the original Orleans duplication question remains separately open
2026-09-11 13:45 UTC — Run
  • 🏷️ Labelled #473 with bug, compatibility, blocked: awaiting-fsharp-feature
  • 🏷️ Labelled #466 with enhancement, feature request, needs triage
  • 🏷️ Labelled #452 with bug, needs investigation, compatibility
  • 💬 Commented on #473: reproduced the reported Debug-mode taskSeq truncation locally, root-caused it to an upstream F# compiler regression (dotnet/fsharp#20466), and pointed to the in-progress fix (dotnet/fsharp#20469) plus a Release-build workaround
2026-09-04 — Run
  • 🔧 Created PR: test: add SideEffects module to TaskSeq.ReplicateInfinite.Tests.fs and TaskSeq.ThreadState.Tests.fs — build succeeds, full suite 4469 passed / 0 failed
  • 📁 Closed #465 (August 2026 monthly activity) and opened this issue for September

Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38

Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@4bc8419fad05e6b032741cbfd189986700bcf71c
Lingua principale
F#
Stelle
111
Fork
13
Merge medio
7h 59m
PR unite (30g)
3

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fsprojects/FSharp.Control.TaskSeq

Tutte le issue di fsprojects/FSharp.Control.TaskSeq

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.