fix(crosscode): scope tunnel identity per project directory - #86
Merged
Conversation
…etry Same IPv6 ETIMEDOUT root cause as web: prod DNS returns IPv6 addresses with no route. Force IPv4 for *.neon.tech, auto-convert to -pooler host, retry API key validation 3x on ETIMEDOUT. Co-authored-by: muse-spark-1.2 <muse-spark@users.noreply.github.com>
Each project directory now gets its own projectId, sessionToken, and cloudflared named tunnel so concurrent sessions no longer share the same tunnel ID. Co-authored-by: muse-spark-1.2 <muse-spark@users.noreply.github.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.
Each project directory now gets its own projectId, sessionToken, and cloudflared named tunnel (keyed by sha256 of cwd in ~/.crosscode/config.json under projects{}), so concurrent sessions in different directories no longer share the same tunnel ID and replace each other server-side.
Includes one-time migration of legacy global identity into the current project's entry.