-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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: upgrade bullmq versions #3105
Conversation
return { | ||
...this.bullConfig, | ||
lockDuration: 90000, | ||
concurrency: 200, | ||
settings: { | ||
backoffStrategies: this.getBackoffStrategies(), | ||
backoffStrategy: this.getBackoffStrategies(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was refactored to a function instead of object since version 2
public createScheduler(name: string, config: QueueBaseOptions) { | ||
this._queueScheduler = new QueueScheduler(name, config); | ||
|
||
return this._queueScheduler; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scheduler is not needed because it is now taken care of by the Worker class
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good improvements.
🌟
@@ -214,24 +209,18 @@ export class WorkflowQueueService { | |||
} | |||
|
|||
private getBackoffStrategies = () => { | |||
return { | |||
[BackoffStrategiesEnum.WEBHOOK_FILTER_BACKOFF]: async ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The enum is not needed now then. 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still use it to specify when adding the actual job, it is accessed in the "Type" param. For now we only have one type, but might expand it in the future so will leave this for now
…into align-bullmq-versions
What change does this PR introduce?
We have mismatched version between the difference services. Updated all versions to be the same.