-
Notifications
You must be signed in to change notification settings - Fork 69
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
This should never happen ... data_receiver.pony line 204 #3053
Comments
Full logs are at http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.1573183987.tar.gz |
I've followed your links, but I can't find a version of the code where line
204 is a Fail(). Can you add the failing code context to this?
…On Fri, Nov 8, 2019 at 4:33 AM Scott Lystig Fritchie < ***@***.***> wrote:
Full logs are at
http://wallaroolabs-dev.s3.amazonaws.com/logs/logs.1573183987.tar.gz
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3053>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEC3TFAYZ4TLVMEZMGWTI3QSTMZ7ANCNFSM4JKSDKHA>
.
|
The gist mentioned in the description text is the small patch that disrupts the line numbers.
|
I've messed up the description of this problem, sorry, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug, feature request, or feedback?
Bug
What is the current behavior?
Intermittent failure during crash & restart of both workers + connector sink in a 2-worker cluster:
The 2nd-to-last log message comes from this small patch at https://gist.github.com/slfritchie/652d3765e0fb4cd6ad59b55899014f81. This patch also affects the line number reported by the
Fail()
statement.What is the expected behavior?
No crash
What OS and version of Wallaroo are you using?
Ubuntu 16.04/Xenial + master branch at commit 4323b71 +
connector-sink-fixes
branch/PR #3042Steps to reproduce?
The text was updated successfully, but these errors were encountered: