-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unnamed module @45312be2 #311
Comments
Hi @ilyas2016 , what java version are you using ? can you provide a minimal sample reproducer project which we can build and test ? |
another thing: can you try to add the following dependency (if you don't already have it) and tell me if you still observe the issue ? io.micrometer:context-propagation:1.0.0 |
Hey @pderop After adding this dependency Exception is not more occurring. It resolved the issue. I am using jdk 17 and while running test cases getting below warning on console.
|
ok, thanks for coming back to me. I also have reproduced the issue. So , if possible, please use the dependency as a work around until we figure out how to avoid this problem. I'm leaving this issue open for the moment. |
Perfect. thanks for the support |
Hi @ilyas2016 , I prefer to close this issue since there is a work around. Thanks. |
Related to #71 and to raphw/byte-buddy#780 |
reactor/reactor-core#3337 should avoid the log. |
* create SpaWebFilterIT for reactive app * change generator for SpaWebFilterIT * fix typo * fix NoSuchTypeException see reactor/BlockHound#311 (comment) * fix testFilterDoesNotForwardToIndexForApi * fix 500 in testFilterDoesNotForwardToIndexForV3ApiDocs see springdoc/springdoc-openapi#1759 * minor fix * remove excludeWebapp in backend:unit:test * add SpaWebFilterTestController to return test index html * fix typo * fix extension * change generator.spec.mts.snap and fix testFilterDoesNotForwardToIndexForApi
I am using blockhound in unit tests only. everything was working fine.
But after i upgraded to spring boot 3. it started printing below stack trace on each test.
The text was updated successfully, but these errors were encountered: