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: don't reschedule delay timer if closing #2535

Merged
merged 1 commit into from
Feb 3, 2023

Conversation

hendrikmoree
Copy link
Contributor

It's sometimes possible the close of bull does not correctly stop the update timer. In some circumstances the update time is stil active after the close call is finished.

Our process hangs on stopping if the timer is active. Tried multiple times with this fix, and our process always stops

Copy link
Member

@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.

Ok, I studied the code and indeed it seems like without that check it could in some edge cases hang up in an infinite timer.

@manast manast merged commit 8a0292a into OptimalBits:develop Feb 3, 2023
github-actions bot pushed a commit that referenced this pull request Feb 3, 2023
## [4.10.3](v4.10.2...v4.10.3) (2023-02-03)

### Bug Fixes

* don't reschedule delay timer if closing ([#2535](#2535)) ([8a0292a](8a0292a))
@manast
Copy link
Member

manast commented Feb 3, 2023

🎉 This PR is included in version 4.10.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@manast manast added the released label Feb 3, 2023
@hendrikmoree hendrikmoree deleted the close-timer branch February 3, 2023 09:57
@hendrikmoree
Copy link
Contributor Author

Awesome! Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants