[Bug]: tailscale command can be slow on some machines
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with tailscale.ts and inspect how TAILSCALE_STATUS_TIMEOUT is applied when checking Tailscale availability. The report says the command can take 1.8–2.6 seconds on Windows, while the current timeout is 1.5 seconds; reproduce with a slow response and check whether a larger timeout or configurable override fits the project. Done means Tailscale is detected when available despite the reported delay.
Written by the indexing model from the issue text.
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
- Start the app with slow tailscale (ie. on Windows)
- Tailscale option in settings is disabled
Expected behavior
If Tailscale is available, T3 should expose it.
Actual behavior
Tailscale is available, but T3 fails to detect it.
Impact
Major degradation or frequent failure
Version or commit
main 8f75697b9e022033f2615cb32e3c6ddc61c52353
Environment
Windows 11
Logs or stack traces
Tailscale takes about 1.8–2.6s to answer when an app like T3 Code runs it. From a plain terminal it's a bit faster, around 0.9s.
Changing tailscale.ts from
export const TAILSCALE_STATUS_TIMEOUT = Duration.millis(1_500);
to:
export const TAILSCALE_STATUS_TIMEOUT = Duration.seconds(5);
resolves the issue. There could be a config option or override or just larger timeout.
Screenshots, recordings, or supporting files
No response
Workaround
Modify tailscale.ts locally and run a dev version or patch asar locally.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 8h 34m
- Merged PRs (30d)
- 243
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
[Bug]: Dead-key apostrophe inserts extra quotes in the composerPossibly taken A pull request linked to this issue is open or already merged. Openbug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pingdotgg/t3code#16859 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pingdotgg/t3code#16822 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pingdotgg/t3code#16821 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pingdotgg/t3code#16810 · 2 comments ·
Maintainers usually reply within 1 day
-
[Bug]: Antigravity turns fail on NixOS: embedded Python can't verify TLS (empty CA store) -> 502Openbug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#16742 · 1 comment ·
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
farbenmeer/tapi#531 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
naver/egjs-flicking#971 ·
-
Renderer treats a sub-pixel width difference as a resize, which cancels the `motion()` entranceOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Tenant
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MTES-MCT/Dossier-Facile-Frontend#2061 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
backnotprop/plannotator#1784 ·
Maintainers usually reply within 1 day