DopplerHQ / DopplerHQ/cli-action
Action regularly fails due to timeouts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 65
- Forks
- 16
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 1
Description
When using this action, we see regular failures due to the download action taking longer than 30s:
the entire job fails after that. Since the Github action is fairly simple, we can switch to fetching the CLI directly. When we do that, the CI timings show that downloading Doppler CLI usually takes about 1s, but occasionally spikes to even one minute (less on the screenshot but it's an example):
It would be useful if this action
- didn't fail when the downloading takes more than 30s, or retried the download a couple of times
- cached the actual CLI tool (instead of the install script) so the downloading isn't necessary on each build
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 tracing the GitHub Action's download and install step, using the timeout and CI timing behavior described in the issue as the baseline. Done means transiently slow downloads no longer fail immediately or are retried, and repeated builds can use a cached CLI instead of downloading it each time; verify the behavior in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100