Home Original page

BlockHound support by bsideup · Pull Request #1682 · reactor/reactor-core

simonbasle

simonbasle

simonbasle added a commit that referenced this pull request

May 3, 2019 
Add BlockHound SPI's implementation. By keeping it next to core,
we control how we intercept the tasks (e.g., `onScheduleHook`)
and can also apply internal optimizations in future.

BlockHound's built-in Reactor integration will be adjusted to not
apply anything if Reactor's version is 3.3 or higher.

The integration class must be public to to the ServiceLoader
use, but it is excluded from javadoc and documented inline as
"do not consider public".
The regular expression in the gitignore file was way too broad,
which prevents a SPI file to be committed.
Add BlockHound SPI's implementation. By keeping it next to core,
we control how we intercept the tasks (e.g., `onScheduleHook`)
and can also apply internal optimizations in future.

BlockHound's built-in Reactor integration will be adjusted to not
apply anything if Reactor's version is 3.3 or higher.

The integration class must be public to to the ServiceLoader
use, but it is excluded from javadoc and documented inline as
"do not consider public".

@bsideup bsideup deleted the add_blockhound_spi branch

May 4, 2019 07:28

bsideup added a commit to reactor/BlockHound that referenced this pull request

May 5, 2019 
#29)

Since reactor/reactor-core#1682 is merged now, we should not instrument Reactor because it natively integrates with BlockHound via the SPI

smaldini pushed a commit that referenced this pull request

May 6, 2019 
Add BlockHound SPI's implementation. By keeping it next to core,
we control how we intercept the tasks (e.g., `onScheduleHook`)
and can also apply internal optimizations in future.

BlockHound's built-in Reactor integration will be adjusted to not
apply anything if Reactor's version is 3.3 or higher.

The integration class must be public to to the ServiceLoader
use, but it is excluded from javadoc and documented inline as
"do not consider public".