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.

Sign up for GitHub

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

Jump to bottom

fix(worker): evaluate if a job needs to be fetched when moving to failed #3043

Merged
merged 1 commit into from
Feb 2, 2025
Merged

fix(worker): evaluate if a job needs to be fetched when moving to failed #3043

merged 1 commit into from
Feb 2, 2025
+5 −1

Conversation

roggervalf
Copy link
Collaborator

Why

  1. Why is this change necessary? No need to fetch need job always when moving a job to failed, need to use similar logic as we do with move to completed

How

  1. How did you implement this? Use same logic as in move to completed

Additional Notes (Optional)

Any extra info here.

@roggervalf roggervalf merged commit 406e21c into master Feb 2, 2025
10 of 11 checks passed
@roggervalf roggervalf deleted the worker-failed-fetch-next branch February 2, 2025 02:21
github-actions bot pushed a commit that referenced this pull request Feb 2, 2025
@semantic-release-bot
chore(release): 5.39.2 [skip ci]
56aabb0 
## [5.39.2](v5.39.1...v5.39.2) (2025-02-02)

### Bug Fixes

* **worker:** evaluate if a job needs to be fetched when moving to failed ([#3043](#3043)) ([406e21c](406e21c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@roggervalf