Implement periodic unlock of linked telescope anomalies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We need a Go job that will automatically unlock one linked_anomalies row per user (where automaton = 'Telescope' and unlocked = false) at specific times of the week.
The logic should:
• Only unlock one row per user at a time
• Space unlocks based on how much time is left in the week (ending Sunday 00:00 AEST)
• Skip users if they’ve already unlocked too many anomalies too quickly
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 file, test, or entry point is named. Start by locating the Go job and the linked_anomalies table, then clarify the weekly schedule, the unlock limit, and the definition of unlocking too quickly. Done means the job consistently applies the agreed rules and has coverage for one-per-user, timing, and skip cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100