Philippus Baalman
Philippus Baalman
> Would you please create a new version branch? Then I'll start working on a new PR from the release branch I've created the `series/9.x` branch.
Ideally we would indeed switch to testcontainers-scala, a PR would be very welcome. It would also be very nice to have the tests that require an elasticsearch instance separate in...
I think adding a new client is fine, provided someone is using it in production (like you). Maybe we can mark it as experimental, allowing us to make backwards incompatible...
@igor-vovk now that https://github.com/Philippus/elastic4s/pull/3124 is merged, care to get back to this PR and clean it for merging (or create a new one based on the current main branch)?
@lenguyenthanh Do you have time to take a look at the PR to see if this will work for you as well?
I think it's because of all the tests running on the same instance. If you change the test to "yellow" or "green" I think it will be fine. Even "red"...
> @Philippus I think what happens is that this status changes from `red` to `yellow` and then to `green` (doc https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html). And then depending on when the test runs it...
Do you have a minimal reproducer somewhere? Then someone can take a look.
https://codeberg.org/sciss/SwingPlus dropped support for scala 2.11 as well.
This PR is mostly been superseded by other Pull Requests. I created an [issue](https://github.com/scala/scala-swing/issues/187) about dropping support for Scala 2.11.