You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/12/05 22:07:29 UTC
[GitHub] [pulsar-client-reactive] cbornet opened a new issue, #85: Add tests with BlockHound
cbornet opened a new issue, #85:
URL: https://github.com/apache/pulsar-client-reactive/issues/85
It would be nice to add BlockHound tests to check that we're not blocking accidentally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add tests with BlockHound [pulsar-client-reactive]
Posted by "AbaSheger (via GitHub)" <gi...@apache.org>.
AbaSheger commented on issue #85:
URL: https://github.com/apache/pulsar-client-reactive/issues/85#issuecomment-4531765567
Hi, I’d like to take a look at this.
From what I understand, the goal is to add BlockHound-based tests to verify that the reactive client does not accidentally perform blocking calls on non-blocking threads.
My first step would be to inspect the existing test setup, check how reactive behavior is currently tested, and add a small focused test following the project’s current style.
Does that sound like the right direction?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org