Unclear error when subject isnt correct
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- ci-cd
Research direction
Start by reproducing the workflow with a subject in the repo:org/repo form that omits the required suffix, then trace where the action reports the failed tailscale up attempt. Done means the malformed subject produces a specific, useful error instead of the repeated generic sudo failed with exit code 1 message.
Written by the indexing model from the issue text.
Description
I had a subject of form repo:org/repo missing e.g., a :* at the end
the error you get from this action in this case is not very helpful/misleading:
▶️ get tailscale status
Daemon ready! Initial state: NeedsLogin
✅ tailscaled daemon is up and running!
▶️ hostname
Attempt 1 to bring up Tailscale...
▶️ tailscale up
Warning: Tailscale up attempt 1 failed: sudo failed with exit code 1
Retrying in 2 seconds...
Attempt 2 to bring up Tailscale...
▶️ tailscale up
Warning: Tailscale up attempt 2 failed: sudo failed with exit code 1
Retrying in 4 seconds...
Attempt 3 to bring up Tailscale...
▶️ tailscale up
Warning: Tailscale up attempt 3 failed: sudo failed with exit code 1
Retrying in 6 seconds...
Attempt 4 to bring up Tailscale...
▶️ tailscale up
Warning: Tailscale up attempt 4 failed: sudo failed with exit code 1
Retrying in 8 seconds...
Attempt 5 to bring up Tailscale...
▶️ tailscale up
Warning: Tailscale up attempt 5 failed: sudo failed with exit code 1
Error: sudo failed with exit code 1
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 tailscale/github-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tailscale/github-action#283 · 1 comment · 1 reaction ·
-
fr
Difficulty 3/5 1-2 days Newbie friendliness 68/100
tailscale/github-action#317 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
tailscale/github-action#316 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
tailscale/github-action#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
tailscale/github-action#313 · 1 reaction ·
All issues in tailscale/github-action
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·