-
Notifications
You must be signed in to change notification settings - Fork 81
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
Apparent double-notify or notify-on-construction-step downstream of partitioned table transform #3127
Comments
Full stack trace from one user:
|
Current theory involves partitioned table transformations. |
From the TableReplayer occurence (partial stack trace):
I'll see if I can get any more information. |
This is completely distinct. Please file a separate issue for the bug in |
I don't have anything in the user's logs that can help narrow this down, but after substantial testing and code evaluation I'm pretty sure partitioned table transform manages dependencies correctly. I've done some optimization and some tightening for error handling, but no reason to think I've isolated the issue. |
The change that merged includes the aforementioned optimization and error checking, but also changes how swap listeners work to avoid redundant, hard-to-break links in the notification-delivery DAG. I'm optimistic that this will drop the noise level if there is in fact an issue of the postulated type. |
I don't have enough history to know if this report was discovered with parallelism enabled, or not. If yes, I think the issue was a double-dispatch due to an error in the way |
Description
The above error has been raised (part of a bigger stack trace) in two cases:
This could be a double-notification bug, or something else.
Steps to reproduce
This was encountered by two end-users. I don't have the exact code they ran to make it happen.
Expected results
Tables merging, and data being played back.
Actual results
The stack trace.
Additional details and attachments
I don't have any at the moment. I will paste them in comments below
Versions
The text was updated successfully, but these errors were encountered: