Another strong +1 to have Harry in-tree, and another +1 to building shaded dtest JARs on release. There are a number of projects that would benefit from having these JARs available in a central repository, like Sidecar, Driver, etc. I didn't see a ticket so created one: https://issues.apache.org/jira/browse/CASSANDRA-19113
> On Nov 28, 2023, at 3:12 AM, Alex Petrov <al...@coffeenco.de> wrote: > > Sure, that should be possible. I will check and will get back. > > On Mon, Nov 27, 2023, at 10:10 PM, Ekaterina Dimitrova wrote: >> +1, also, Alex, just an idea - maybe you want to make a virtual talk, as >> part of the contributors meetings? >> >> >> На понеделник, 27 ноември 2023 г. Yifan Cai <yc25c...@gmail.com >> <mailto:yc25c...@gmail.com>> написа: >> +1 >> >> >> 发件人: Sam Tunnicliffe <s...@beobal.com <mailto:s...@beobal.com>> >> 发送时间: Tuesday, November 28, 2023 2:43:51 AM >> 收件人: dev <dev@cassandra.apache.org <mailto:dev@cassandra.apache.org>> >> 主题: Re: [DISCUSS] Harry in-tree >> >> Definite +1 to bringing harry-core in tree. >> >>> On 24 Nov 2023, at 15:43, Alex Petrov <al...@coffeenco.de >>> <mailto:al...@coffeenco.de>> wrote: >>> >>> Hi everyone, >>> >>> With TCM landed, there will be way more Harry tests in-tree: we are using >>> it for many coordination tests, and there's now a simulator test that uses >>> Harry. During development, Harry has allowed us to uncover and resolve >>> numerous elusive edge cases. >>> >>> I had conversations with several folks, and wanted to propose to move >>> harry-core to Cassandra test tree. This will substantially >>> simplify/streamline co-development of Cassandra and Harry. With a new >>> HistoryBuilder API that has helped to find and trigger [1] [2] and [3], it >>> will also be much more approachable. >>> >>> Besides making it easier for everyone to develop new fuzz tests, it will >>> also substantially lower the barrier to entry. Currently, debugging an >>> issue found by Harry involves a cumbersome process of rebuilding and >>> transferring jars between Cassandra and Harry, depending on which side you >>> modify. This not only hampers efficiency but also deters broader adoption. >>> By merging harry-core into the Cassandra test tree, we eliminate this >>> barrier. >>> >>> Thank you, >>> --Alex >>> >>> [1] https://issues.apache.org/jira/browse/CASSANDRA-19011 >>> [2] https://issues.apache.org/jira/browse/CASSANDRA-18993 >>> [3] https://issues.apache.org/jira/browse/CASSANDRA-18932
