-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
Blocking call in UnixResolverDnsServerAddressStreamProvider.parse #10925
Comments
@violetagg can you provide a PR ? |
@normanmaurer I was thinking for allowing blocking calls when loading |
This sounds good |
normanmaurer
pushed a commit
that referenced
this issue
Jan 14, 2021
…rse (#10935) Motivation: Internally UnixResolverDnsServerAddressStreamProvider#parse calls FileInputStream.read(...) when parsing the etcResolverFiles. This will cause the error below when BlockHound is enabled reactor.blockhound.BlockingOperationError: Blocking call! java.io.FileInputStream#readBytes at java.io.FileInputStream.readBytes(FileInputStream.java) at java.io.FileInputStream.read(FileInputStream.java:255) Modifications: - Add whitelist entry to BlockHound configuration - Add test Result: Fixes #10925
normanmaurer
pushed a commit
that referenced
this issue
Jan 14, 2021
…rse (#10935) Motivation: Internally UnixResolverDnsServerAddressStreamProvider#parse calls FileInputStream.read(...) when parsing the etcResolverFiles. This will cause the error below when BlockHound is enabled reactor.blockhound.BlockingOperationError: Blocking call! java.io.FileInputStream#readBytes at java.io.FileInputStream.readBytes(FileInputStream.java) at java.io.FileInputStream.read(FileInputStream.java:255) Modifications: - Add whitelist entry to BlockHound configuration - Add test Result: Fixes #10925
ZzxyNn
pushed a commit
to ZzxyNn/netty
that referenced
this issue
Jan 29, 2021
…rse (netty#10935) Motivation: Internally UnixResolverDnsServerAddressStreamProvider#parse calls FileInputStream.read(...) when parsing the etcResolverFiles. This will cause the error below when BlockHound is enabled reactor.blockhound.BlockingOperationError: Blocking call! java.io.FileInputStream#readBytes at java.io.FileInputStream.readBytes(FileInputStream.java) at java.io.FileInputStream.read(FileInputStream.java:255) Modifications: - Add whitelist entry to BlockHound configuration - Add test Result: Fixes netty#10925
raidyue
pushed a commit
to raidyue/netty
that referenced
this issue
Jul 8, 2022
…rse (netty#10935) Motivation: Internally UnixResolverDnsServerAddressStreamProvider#parse calls FileInputStream.read(...) when parsing the etcResolverFiles. This will cause the error below when BlockHound is enabled reactor.blockhound.BlockingOperationError: Blocking call! java.io.FileInputStream#readBytes at java.io.FileInputStream.readBytes(FileInputStream.java) at java.io.FileInputStream.read(FileInputStream.java:255) Modifications: - Add whitelist entry to BlockHound configuration - Add test Result: Fixes netty#10925
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
No blocking calls reported by BlockHound
Actual behavior
The exception below appears when BlockHound is installed
Netty version
4.1.57.Final
JVM version (e.g.
java -version
)JDK 8
OS version (e.g.
uname -a
)MacOS
The text was updated successfully, but these errors were encountered: