Vladimir Sitnikov

> I haven't seen a structural approach to stateful generations of actions anywhere I mean more like unparse to a structured form rather than "use structural approach for generation". For...

I've created https://github.com/jlink/jqwik/issues/447 for tracking "generate test source code" feature.

I am indifferent to ChainSpec, as it does not help shrinking in my case.

>Use an immutable, side-effect-free model-based approach I do not see how `immutable, side-effect-free model-based approach` can help me. > Use the spec to insert (de-)serialiser for enabling more shrinking steps...

Of course, wrong-state object issue goes away, however, shrinking goes away as well 🤷

That's fair. When I created the issue, I thought resolving it would enable me to activate shrinking. Unfortunately the shrinking is inefficient, so I have to keep it disabled. For...

Would you please outline a testing problem? I guess https://github.com/google/guice/wiki/CustomScopes addresses a related issue, so it might be their API would work for an inspiration.

> It seems to me that the essence of the problem is the clarity of the warning message The essence is that the end-users can't fix the issue at their...

> Users can remove the status attribute and fall back to the default behavior. Let me try again: the warning talks to wrong people. JMeter application users can't fix their...

>Since https://github.com/apache/jmeter/commit/cbdfd1ba435ad92b32c6538a5a433ac7dff9e024 has entered the master branch, it seems that there is no point in opening the current issue. I would still like to migrate off log4j2