pingdotgg / pingdotgg/t3code

[Bug]: WSL + T3 Connection not publishing workspaces

Open
#5,210 7 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce

I am using full only WSL with T3 connect, but cannot publish any workspaces to T3 connect, see attached screenshot. Are there any missing packages I need to install, to make it work with WSL?

Image
Expected behavior

Should let me publish the workspaces

Actual behavior

Hangs, see screenshot for error

Impact

Major degradation or frequent failure

Version or commit

No response

Environment

Windows 11 w/ WSL 2.0 and Ubuntu

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The reported area is apps/web; start by reproducing the workspace-publishing flow under Windows 11 with WSL 2.0 and Ubuntu, using the attached screenshot as the only reported error detail. Compare the failing behavior with a working environment and capture the missing error or logs; done when a WSL setup can publish workspaces without hanging.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, typescript, ubuntu
Domain
devops, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.