tailscale / tailscale/github-action
Unclear error when subject isnt correct
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
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
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.
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.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100