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(job): consider changing priority to 0 #2599

Merged
merged 4 commits into from
Jun 28, 2024
Merged

Conversation

roggervalf
Copy link
Collaborator

@roggervalf roggervalf commented Jun 8, 2024

No description provided.

@roggervalf roggervalf force-pushed the change-priority-0 branch 2 times, most recently from 25fa8f6 to 8037e5a Compare June 13, 2024 05:33
Copy link
Contributor

@manast manast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a small comment.

readdJobWithNewPriority( prioritizedKey, markerKey, target,
KEYS[5], ARGV[4] == '1', priority, jobId, isPaused)
elseif rcall("LREM", target, -1, jobId) > 0 then
readdJobWithNewPriority( prioritizedKey, markerKey, target,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe easier to read with "reAddJobWithNewPriority", first time I saw it I thought it was a typo.

@roggervalf roggervalf merged commit 4dba122 into master Jun 28, 2024
10 of 11 checks passed
@roggervalf roggervalf deleted the change-priority-0 branch June 28, 2024 12:26
github-actions bot pushed a commit that referenced this pull request Jun 28, 2024
## [5.8.3](v5.8.2...v5.8.3) (2024-06-28)

### Bug Fixes

* **job:** consider changing priority to 0 ([#2599](#2599)) ([4dba122](4dba122))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants