Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Permanently enqueued provisioner jobs affect the position in queue #16488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
deansheather opened this issue Feb 7, 2025 · 1 comment
Open
Assignees
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic

Comments

@deansheather
Copy link
Member

Related to #15843
Related to #12331

If you have a job that is permanently stuck in queue due to e.g. incorrect provisioner tags, it will impact the "position in queue" for every workspace that enters the job queue.

This results in incorrect labels on workspaces saying "Position in queue; 21" when in reality they are position 1 in queue with the current set of available provisioners.

To fix this we could add a new case to the existing hangdetector code to cancel jobs that have been stuck pending for an hour or so. The queue position calculation logic should probably also be made smarter (see #15843).

Image

https://codercom.slack.com/archives/C06T78M7X7H/p1738927399726959

@deansheather deansheather added the needs-triage Issue that require triage label Feb 7, 2025
@matifali matifali added s3 Bugs that confuse, annoy, or are purely cosmetic and removed needs-triage Issue that require triage labels Feb 13, 2025
@matifali
Copy link
Member

@bartekgatzcoder, this looks related to the Provisioner UI rework.

@ibetitsmike ibetitsmike self-assigned this Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic
Projects
None yet
Development

No branches or pull requests

3 participants