Open OliverO2 opened 5 months ago
The error complains about our reflect library and we (coroutines) are unlikely to ship BH rules for anything but coroutines themselves.
Would it work for you to add a rule in your project for the whole Kotlin reflect package?
On a side note, the fact that renderToString
acquires a global lock is issue on its own, but alas it's more complicated then "just fix it"
we (coroutines) are unlikely to ship BH rules for anything but coroutines themselves.
for the whole Kotlin reflect package?
A bit scary, given that reflection can execute arbitrary user-supplied code.
The error complains about our reflect library and we (coroutines) are unlikely to ship BH rules for anything but coroutines themselves.
Surely a balancing issue, just thought to let you know because some reflection allowance was already there.
Would it work for you to add a rule in your project for the whole Kotlin reflect package?
Sure, no big deal. [Edit: Not the whole package, but selected reflection functions.]
On a side note, the fact that renderToString acquires a global lock is issue on its own, but alas it's more complicated then "just fix it"
Agreed.
kotlinx-coroutines-debug:1.8.0
This one appeared once when running Kotest in debug mode with
env KOTEST_DEBUG=true ./gradlew ...
:Might be worth adding an allowance to
BlockHound.Builder.allowBlockingCallsInReflectionImpl()
at whatever level is deemed appropriate.