fix(pump): vendor @flowcore/data-pump 0.21.4 (hung-connect self-heal)#90
Merged
Conversation
…self-heal) Bumps the vendored data-pump (dnt inlines the jsr import into the published package, pinned by deno.lock) from 0.21.3 to 0.21.4, which adds the hung-connect fix: notifier.waitWebSocket now arms the re-poll timeout + abort BEFORE connect() and races connect() against the resolution promise, so a hung websocket reconnect degrades to a bounded re-poll and auto-recovers to WS mode instead of wedging the pump until a process restart. This is the delivery vehicle that gets the fix into embedded consumers (control-plane, worker, klokkan-backend, usable-chat, ...). See flowcore-io/data-pump#78 (data-pump 0.21.4). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…e host The "missing connection information" test dials a nonexistent host and asserted the error message contains "ENOTFOUND", but some runners' DNS resolvers report an unresolvable host as "EAI_AGAIN" instead (both mean the host did not resolve). Assert on either to de-flake CI. Unrelated to the data-pump bump; pre-existing fragility surfaced on the current runner. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Bumps the vendored
@flowcore/data-pumpfrom 0.21.3 → 0.21.4. dnt inlines this jsr import into the published package (pinned bydeno.lock), so this is the delivery vehicle that gets data-pump's hung-connect fix into every embedded consumer (control-plane, worker, klokkan-backend, usable-chat, …).data-pump 0.21.4 (flowcore-io/data-pump#78):
notifier.waitWebSocketarms the re-poll timeout + abort beforeconnect()and racesconnect()against the resolution promise — so a hung websocket reconnect degrades to a bounded re-poll and auto-recovers to WS mode instead of wedging the pump until a process restart. 2.4.4 vendored 0.21.3 (has #72/#74 self-heal but not this); pathways 2.3.0 vendored 0.19.1 (none).Surgical diff: only the data-pump entry in
deno.json+deno.lock.Test plan
deno task test— 148 non-DB steps pass with 0.21.4 (local DB tests + local dnt build are env-limited; CI runs both clean)🤖 Generated with Claude Code