Repository navigation
fix: work around RTK v0.36.0 GDPR consent hang in non-interactive builds - #80
Merged
Merged
Conversation
RTK ≥0.36.0 added a telemetry consent prompt that blocks on stdin, hanging indefinitely in Docker/devcontainer builds. Add `timeout 10` to kill the process after hook setup completes, and set RTK_TELEMETRY_DISABLED=1 as defense-in-depth. Temporary workaround until upstream fix lands: rtk-ai/rtk#1307 Closes #77
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.
What
Prevents
rtk initfrom hanging indefinitely during devcontainer/Docker builds due to the GDPR telemetry consent prompt introduced in RTK v0.36.0.Why
RTK v0.36.0 added an interactive telemetry consent gate that blocks on stdin. In non-interactive environments (devcontainer
postCreateCommand, Docker entrypoints), there's no stdin — so the process hangs forever, preventing containers from starting.Changes
timeout 10to allrtk initinvocations so the process is killed after hook setup completes (the consent prompt is the only thing that blocks past that point)RTK_TELEMETRY_DISABLED=1as defense-in-depth to disable data collection.devcontainer/init-plugins.sh,claude-code/.devcontainer/init-plugins.sh,ralphex-fe/init-docker.shNotes
This is a temporary workaround until the upstream fix lands: rtk-ai/rtk#1307. All three patched files have a
WORKAROUNDcomment with the upstream link so it can be cleaned up later.Closes #77