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
orderBy.limit changefeed segfault / not working #4850
Comments
Valgrind output when running the
|
Looking at this now. |
This appears to be a data explorer bug, so kicking over to @deontologician . |
@mlucy -- perhaps I'm misunderstanding the issue, but how could a segfault + valgrind memory errors be a data explorer bug? |
The segfault is in next and 2.1.x, OTS by @danielmewes (commits a734dcc and 6167e89). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reported by @oldlam in #4769 (comment) :
I couldn't reproduce the segfault on Linux, but I'm also either not getting any results on the changefeed (not even initial results), or I'm getting initial results but not the update for the
bbb
row.Which of those two happens appears to depend on which build I'm using (debug mode with Clang vs. a release mode binary from the Ubuntu package).
@mlucy could you check this out please?
The text was updated successfully, but these errors were encountered: