Repository navigation
refactor: replace duplicated concurrency schedulers - #520
Merged
Merged
Conversation
Medformatik
enabled auto-merge (squash)
October 18, 2026 21:36
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Replace six duplicated batch schedulers with pinned
p-mapand the shared place-enrichment limiter withp-limit. Ordered results, settled provider failures, independent journey/stop-area capture limits, and process-wide enrichment limits remain explicit at their call sites. Remove the generic helper exports and tests that only duplicated library coverage.Fatal batch errors and caller cancellation now stop further dispatch. Provider deadlines and I/O cancellation remain with their owners; active tasks may finish. Transit preparation keeps its explicit aborted result. Reject an
Infinityenrichment setting before constructing the limiter so it cannot silently disable the existing finite cap.Verification
pnpm verify:fullpassed: lint, 30 workspace type tasks, policy checks, generated Entur/SDK/OpenAPI freshness, and 20,334 tests across 1,759 files. 191 tests / 39 files skipped.Release and upgrade impact
No package release: concurrency implementations change private application/framework workspaces; portable extension contracts and published CLI behavior are unchanged.
Product impact: none
No migration or operator action is required. Existing finite enrichment settings and defaults remain valid.