Backport deadlock fix from 2.4 to 2.3

[AlexeyKuznetsov-DD]

Is your feature request related to a problem?

Hi Spock team,

Would it be possible to backport the following fix to the 2.3 branch?

We’re currently relying on the stable 2.3 release series in our production environment and are unable to adopt version 2.4-M6 at this time due to its pre-release status. Having this fix in 2.3 would help us avoid adopting unstable versions while still benefiting from the resolution.

Thanks for considering this!

=============================
Fix possible deadlock when blocking in mock response generators #1910

Fix fallout of #1885 introduced in M2

This actually fixes the issues: #583, #1882, #1899

Describe the solution you'd like

Backport existing fix to stable 2.3

Describe alternatives you've considered

No response

Additional context

No response

[boris-petrov]

Sorry, what do you mean by "production environment"? Spock is a testing framework.

I've been using 2.4-M6 for many months now and it's working great.

[AlexeyKuznetsov-DD]

Sorry, what do you mean by "production environment"? Spock is a testing framework.

I've been using 2.4-M6 for many months now and it's working great.

That means that we are running on CI to test our code before release, for example.
And team prefers to use released versions of libs, rather then not officially released versions.

[AndreasTu]

@AlexeyKuznetsov-DD We do not do backports of such stuff into older releases.
Please use the curent version 2.4-M6 instead.
The M6 is not a nightly build/snapshot or something like that.
You can use such versions in your test environments.

[AlexeyKuznetsov-DD]

@AlexeyKuznetsov-DD We do not do backports of such stuff into older releases. Please use the curent version 2.4-M6 instead. The M6 is not a nightly build/snapshot or something like that. You can use such versions in your test environments.

Sure. Actually we were able to migrate to 2.4-M6.
Just curious - is there any timeline for 2.4 release?