Cronjobs are not randomized
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I noticed some periodic operations run on the 5-minute (or whatever) mark.
From experience gained working at at an unnamed CDN witnessing traffic spikes, you might regret this :)
Keybase GUI Version: 1.0.14-20160315130050+fc26e6b
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
No files, tests, or entry points are named. Start by locating the periodic operations and cronjob scheduling in the Keybase client, then determine which jobs need randomized timing. Done means the relevant scheduled operations no longer align predictably while their intended intervals remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100