Skip to content
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

Fix panic when canonicalizing a jobspec with incorrect job type. #7207

Merged
merged 2 commits into from
Feb 21, 2020

Conversation

jrasell
Copy link
Member

@jrasell jrasell commented Feb 20, 2020

When canonicalizing the ReschedulePolicy a panic was possible if
the passed job type was not valid. This change protects against
this possibility, in a verbose way to ensure the code path is
clear.

closes #7203

api/tasks_test.go Outdated Show resolved Hide resolved
@schmichael
Copy link
Member

Don't forget a CHANGELOG.md entry

When canonicalizing the ReschedulePolicy a panic was possible if
the passed job type was not valid. This change protects against
this possibility, in a verbose way to ensure the code path is
clear.
@jrasell jrasell merged commit 2086bb7 into master Feb 21, 2020
@jrasell jrasell deleted the b-gh-7203 branch February 21, 2020 15:01
notnoop pushed a commit that referenced this pull request Apr 9, 2020
Fix panic when canonicalizing a jobspec with incorrect job type.
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

type = "periodic" seems to trigger a segfault
3 participants