Piotr Smaron
Piotr Smaron
Not sure what to do now, it turned out to be "unsupported" driver, so do we consider the matter settled?
FWIW: In order to fix this issue it's enough to change this class: ``` // data_dictionary.hh:55 class no_such_keyspace : public std::runtime_error ``` to inherit this exception instead: ``` class no_such_keyspace...
I'm closing the Issue, because it appears to be a driver incompatibility at most. cc @dkropachev
> Can you please clarify why exactly you have closed it ? It seemse to me that scylla responses with wrong code. @dkropachev I closed it, because I realized I...
> @ptrsmrn what is the origin of the regression? Was the base class changed in one of the commits in 6.x, and if yes, what was the reason for the...
> Ok, I have rerun test again and here is the buffer scylla responds with: `\x00\x00\x00\x00\x00%Can't find a keyspace not_existing_ks` , it is definnitely returning `code` 0. I believe scylla-server...
> > > Ok, I have rerun test again and here is the buffer scylla responds with: `\x00\x00\x00\x00\x00%Can't find a keyspace not_existing_ks` , it is definnitely returning `code` 0. >...
@mykaul I'd like to return to it some day, but have higher priority items on my plate atm. I think items here make sense and if addresses, can protect us...
@kbr-scylla WDYT?
The newly added testcase failed on: ``` logger.info("waking up the leader to continue processing ALTER on a changed schema, which should cause a retry") > await injection_handler.message() ``` The decoded...