microsoft / microsoft/winget-pkgs
New Pipeline queuing allows duplicate runs / requests
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
With the new pipeline deployment, the queuing doesn't check to see if a request for the same PR is already in the queue. This allows for a single PR to have two runs going concurrently.
I'd expect that if a run is already queued or running, the older request would be removed from the queue and/or the current run would be cancelled.
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 reviewing the new pipeline deployment and the linked pull request #242242, then trace how queued requests for pull requests are represented and processed. Done means a newer request for the same PR does not produce concurrent runs: the older queued request is removed or the current run is cancelled.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100