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): revert console warn custom job ids when they represent integers #2312

Conversation

roggervalf
Copy link
Collaborator

This reverts commit 6e677d2.

@roggervalf roggervalf changed the base branch from master to feat/better-handling-of-queue-markers December 5, 2023 03:50
@roggervalf roggervalf merged commit 84015ff into feat/better-handling-of-queue-markers Dec 5, 2023
11 checks passed
@roggervalf roggervalf deleted the revert-1569-fix-custom-job-ids branch December 5, 2023 03:57
github-actions bot pushed a commit that referenced this pull request Dec 21, 2023
# [5.0.0](v4.17.0...v5.0.0) (2023-12-21)

### Bug Fixes

* **connection:** require connection to be passed ([#2335](#2335)) ([1867dd1](1867dd1))
* **job:** revert console warn custom job ids when they represent integers ([#2312](#2312)) ([84015ff](84015ff))
* **python:** unify redis connection args for Queue and Worker ([#2282](#2282)) ([8eee20f](8eee20f))
* **worker:** throw error if connection is missing ([6491a18](6491a18))

### Features

* **job:** provide skipAttempt option when manually moving a job ([#2203](#2203)) ([0e88e4f](0e88e4f))
* **python:** use new queue markers ([b0a13e8](b0a13e8))
* **python:** use new queue markers ([4276eb7](4276eb7))
* **worker:** improved markers handling ([73cf5fc](73cf5fc))
* **worker:** improved markers handling ([0bac0fb](0bac0fb))

### BREAKING CHANGES

* **worker:** Markers use now a dedicated key in redis instead of using a special Job ID.
* **worker:** Markers use now a dedicated key in redis instead of using a special Job ID.
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