-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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(core): Start WaitTracker only in the main container #9600
Conversation
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.
WaitTracker initialization in the constructor means that as soon as this class enters the DI dependency tree, we start tracking for waiting executions
Thanks for this! Will keep an eye out for timers in constructors.
Tested with single main and with multi-main leader and follower and it works as expected.
✅ All Cypress E2E specs passed |
1 flaky test on run #5291 ↗︎
Details:
cypress/e2e/5-ndv.cy.ts • 1 flaky test
Review all test suite changes for PR #9600 ↗︎ |
Got released with |
We changed WaitTracker to not start the timer in the constructor in #9600. So we don't need to mock it anymore.
WaitTracker
initialization in the constructor means that as soon as this class enters the DI dependency tree, we start tracking for waiting executions, causinggetWaitingExecutions
queries to run even before theexecution_entity
table might be available.This can be verified by using any of the import commands on a new DB on any of the last releases.
Review / Merge checklist