GhostWriters / GhostWriters/docker-packt-cli
[FEAT] Retry on timeout failed
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 10
- Forks
- 4
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 6
Description
Is this a new feature request?
- I have searched the existing issues
Wanted change
Error Handling
Reason for change
Thanks for the nice tool first.
I've been use it for couple of weeks. It was working well.
But in these two days, there are two conditions occurred,
- timeout of anti-captcha
- connection aborted
currently, once i received the email of the failed job, i entered the container to execute the command in crontab manually.
Probably add the feature of retry?
Proposed code change
No response
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 inspecting the container's crontab command and the failure paths associated with anti-captcha timeouts and connection-aborted errors. Determine where a failed job currently stops and what retry behavior is expected, then verify that a failed job can retry without requiring manual command execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100