Docs: local queues use System.Threading.Channels, not TPL Dataflow - #4411
Merged
Merged
Conversation
…ls, not TPL Dataflow Wolverine 5.0 replaced TPL Dataflow with System.Threading.Channels for all in-memory queueing (see the 5.0 migration notes), but the local queue, runtime, and durability pages still described the old Dataflow internals. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPRfTmSLt2W8XBEEtReGab
This was referenced Sep 11, 2026
This was referenced Sep 20, 2026
This was referenced Sep 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wolverine 5.0 replaced TPL Dataflow with
System.Threading.Channelsfor all of its in-memory queueing. The 5.0 migration notes say so, and JasperFx'sBlock<T>is built onChannel<T>. Three pages still described the old Dataflow internals:guide/messaging/transports/local.md: the intro, and the "Configuring Parallelization and Execution Properties" sectionguide/runtime.md: the buffered endpoints descriptionguide/durability/index.md: the outbox message relay descriptionThe only Dataflow mentions left are intentional: the historical 5.0 notes in
migration.md, and a "(Wolverine used TPL Dataflow for this before 5.0)" aside on the local queue page.This PR only changes docs. The local queue page has a related doc problem, filed as #4410:
CircuitBreaker()on a buffered local queue is silently ignored.🤖 Generated with Claude Code
https://claude.ai/code/session_01UPRfTmSLt2W8XBEEtReGab