Batch invalidation
Open
- Dominant language
- Ruby
- Stars
- 98
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We have an initial experiment of this in Campaigns that went well, we could extract this into the gem but we also need to figure out what exactly should happen when a job realizes that its orchestration has been invalidated.
Contributor guide
Research direction
Start by reviewing the initial batch-invalidation experiment in Campaigns and how this gem currently handles job orchestration. Clarify what should happen when a job detects invalidation, then define the extracted behavior and its completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100