Dusan Malusev

@cezarmoise @fruch @soyacz I'm closing this one, as gemini has been backported to all relevant branches and no leak is seen, if it seen we can open a new issue...

> After a rebase, the test of `test_01_gemini_thread` should be adjusted. mainly the variable of `expected_gemini_arguments`, with new values. What needs changing, cause nothing here changes the tests, I've incorporated...

> Need to fix the failed integration test. It is related to the change of parameters for the gemini command. > > Also, split the whole change into 2 commits,...

> Why are we supposed to review 6 commits, each named `"wip"`? Please provide a cover letter and reasonable commit division first. Yes I will rewrite them, just wanted to...

> @CodeLieutenant > > please look at this ASAP, this version was backported into 2025.1 and it breaking everywhere s-b is used Working on it already

> > [@dkropachev](https://github.com/dkropachev) > > [#181](https://github.com/scylladb/scylla-bench/pull/181) demonstrates that gocql version change is the cause, can you assign someone to take a closer look at it ? > > Can you...

> So probably it is the same issue as [#170](https://github.com/scylladb/gocql/issues/444) correct ? Yes

Testing if the driver is behaving correctly https://github.com/CodeLieutenant/gemini-driver-test Gemini Seed: 60 Output: ``` go run main.go -hosts " 192.168.101.2, 192.168.101.3" 2024/10/02 15:07:55 Connected to ScyllaDB: 192.168.101.2, 192.168.101.3 2024/10/02 15:07:55 Creating...

> [@CodeLieutenant](https://github.com/CodeLieutenant) > > what's the difference between this one and [#426](https://github.com/scylladb/gemini/issues/426) > > I think one of them should be closed, and collect in one of the information we...

> * [ ] we need to try gemini with MV enabled on master lastet, where it might been fixed Even if we test against the master, the oracle still...