-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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): Ensure followers do not recover executions from logs #9785
Conversation
) {} | ||
|
||
/** | ||
* Recover key properties of a truncated execution using event logs. | ||
*/ | ||
async recoverFromLogs(executionId: string, messages: EventMessageTypes[]) { | ||
if (this.orchestrationService.isFollower) return; |
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.
Would it make sense to move this check to this line instead?
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.
My reasoning for making the leadership check internal to the service is to prevent someone in future using recoverFromLogs
elsewhere and forgetting to account for leadership. This follows the pattern in WaitTracker
and PruningService
.
✅ No visual regressions found. |
1 flaky test on run #5546 ↗︎
Details:
e2e/5-ndv.cy.ts • 1 flaky test
Review all test suite changes for PR #9785 ↗︎ |
✅ All Cypress E2E specs passed |
Got released with |
1 similar comment
Got released with |
https://linear.app/n8n/issue/PAY-1682