You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While fiddling with it, I noticed that the ch.qos.logback.classic.Logger#buildLoggingEventAndAppend got flagged downstack due to some blocking IO.
Of course I wanted to allow this method but I couldn't find a way to customize BlockHound before initialization since it gets done for me by the BlockHoundTestExecutionListener.java, so I had to:
replace blockhound-junit-platform with blockhound dependency;
So, as per title, is this the right way to allow/disallow custom methods when wanting to use blockhound-junit-platform? Or is there something obvious that I might've missed?
Thanks in advance :)
The text was updated successfully, but these errors were encountered:
Thanks, didn't notice the empty varargs install method loaded all the integrations.
Integrated the change in my demo and everything still works, much better.
Not really an issue, but I couldn't find a gitter channel for BlockHound where I would've asked this question otherwise :)
I'm playing around with BlockHound JUnit Platform for a little demo based on Project Reactor (https://github.com/dsibilio/blockhound-demo).
While fiddling with it, I noticed that the
ch.qos.logback.classic.Logger#buildLoggingEventAndAppend
got flagged downstack due to some blocking IO.Of course I wanted to allow this method but I couldn't find a way to customize BlockHound before initialization since it gets done for me by the BlockHoundTestExecutionListener.java, so I had to:
So, as per title, is this the right way to allow/disallow custom methods when wanting to use blockhound-junit-platform? Or is there something obvious that I might've missed?
Thanks in advance :)
The text was updated successfully, but these errors were encountered: