Possible wrong default constant to update apt cache.
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
https://github.com/debops/debops/blob/7819117781955a60adffcbedd9cd73787326b00c/ansible/roles/python/tasks/main_raw.yml#L14
https://github.com/debops/debops/blob/7819117781955a60adffcbedd9cd73787326b00c/ansible/roles/python/defaults/main.yml#L34
Shouldn't python__raw_apt_cache_valid_time be in minutes? Like 12h * 60 min/h = 720 min ?
Contributor 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.
Research direction
Start by comparing ansible/roles/python/tasks/main_raw.yml at line 14 with ansible/roles/python/defaults/main.yml at line 34. Check how python__raw_apt_cache_valid_time is consumed and what unit the task expects. Done means the default and its documented or implied 12-hour value use the same unit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100