You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In next, this only occurs with -i rb, but that is probably because only the ruby client uses parallel query execution at the moment. This was built with gcc.
Start of the crash:
error: Error in ../src/rdb_protocol/changefeed.cc at line 1484:
error: Guarantee failed: [queued_changes.size() == 0]
error: Backtrace:
error: Wed Feb 11 15:14:40 2015
1: rethinkdb_backtrace(void**, int) at rethinkdb_backtrace.cc:101
2: backtrace_t::backtrace_t() at backtrace.cc:203
3: lazy_backtrace_formatter_t::lazy_backtrace_formatter_t() at backtrace.cc:283
4: format_backtrace(bool) at backtrace.cc:198
5: report_fatal_error(char const*, int, char const*, ...) at errors.cc:83
6: ql::changefeed::limit_sub_t::maybe_start() at changefeed.cc:1484
7: ql::changefeed::limit_sub_t::init(std::vector<std::pair<std::string, std::pair<ql::datum_t, ql::datum_t> >, std::allocator<std::pair<std::string, std::pair<ql::datum_t, ql::datum_t> > > > const&) at changefeed.cc:1606
8: ql::changefeed::msg_visitor_t::operator()(ql::changefeed::msg_t::limit_start_t const&) const::{lambda(ql::changefeed::limit_sub_t*)#1}::operator()(ql::changefeed::limit_sub_t*) const at changefeed.cc:1752
9: std::_Function_handler<void (ql::changefeed::limit_sub_t*), ql::changefeed::msg_visitor_t::operator()(ql::changefeed::msg_t::limit_start_t const&) const::{lambda(ql::changefeed::limit_sub_t*)#1}>::_M_invoke(std::_Any_data const&, ql::changefeed::limit_sub_t*) at functional:1780
10: std::function<void (ql::changefeed::limit_sub_t*)>::operator()(ql::changefeed::limit_sub_t*) const at functional:2162
The text was updated successfully, but these errors were encountered:
@mlucy: Yes. What was the bug? Does the crash happen without parallel query execution? I'm mostly curious, and I also want to explain it in the change log.
In
next
, this only occurs with-i rb
, but that is probably because only the ruby client uses parallel query execution at the moment. This was built with gcc.Start of the crash:
The text was updated successfully, but these errors were encountered: