Skip to content

Classify DNS resolution errors as IO_NETWORK - #109

Open
robertbuessow wants to merge 1 commit into
mainfrom
fix/classify-dns-error-as-network
Open

Classify DNS resolution errors as IO_NETWORK#109
robertbuessow wants to merge 1 commit into
mainfrom
fix/classify-dns-error-as-network

Conversation

@robertbuessow

Copy link
Copy Markdown
Contributor

Summary

  • A DNS resolution failure (dns error: proto error: no records found ... from hickory-resolver) didn't match any substring check in classify_message() and fell through to the INTERNAL catch-all, even though it's a network-connectivity condition.
  • Adds "dns error" to the IO_NETWORK pattern list so these classify consistently with other connection failures (refused/reset/timed out).

Test plan

  • cargo test in iceberg_rust_ffi (existing error-classification tests in test/error_tests.jl / Rust unit tests)
  • Manually verify a DNS-unreachable Iceberg REST catalog host now surfaces IcebergException: IO_NETWORK instead of INTERNAL

🤖 Generated with Claude Code

DNS failures (e.g. hickory-resolver's "dns error: proto error: no
records found ...") didn't match any pattern in classify_message()
and fell through to the INTERNAL catch-all, even though they're a
network condition and should surface as IO_NETWORK like other
connectivity failures.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant