Uwe Schaefer

you'll probably want to control it per test, not per container

~~If we wanted to integrate this deeply into the factcast-extension, an alternative would be to use testcontainer's way of initializing the DB:~~ ~~see JdbcDatabaseContainer::withInitScript~~ Edit: Turns out this is not...

But in order to create a fixture, isn't it nicer to publish a bunch of facts via the API ? I feel like this is much more maintainable than having...

That's what i mean: if you publish via API from java, you can get rid of escaping or even writing any json. Isn't that easier to do?

any feedback on this @sschmiedleitner ? One collegue did a @BeforeMethod reading a stream from disk (with unescaped headers & payloads) and used `fc.publish(Fact.of(JsonNode, JsonNode))` from two nodes read from...

related to https://github.com/redisson/redisson/issues/3862

_From @uweschaefer on 2018-11-24 03:00:37 +0000 UTC_ Obviously, the spring boot mechanics prevent this currently: ``` [org.factcast.client.grpc.cli.cli:4599] analysis: 28,517.38 ms error: unsupported features in 14 methods Detailed message: Error: Bytecode...

_From @uweschaefer on 2019-06-20 12:24:36 +0000 UTC_ postponed to 0.2

no it wasn't

Decided to add BatchingFactObserver to prevent possible infinite loop in default methods