Skip to content

fix: swap status monitor dns resolver with native resolver#2432

Closed
MasterPtato wants to merge 1 commit into
05-07-fix_pegboard_fix_netns_path_bugfrom
05-07-fix_swap_status_monitor_dns_resolver_with_native_resolver
Closed

fix: swap status monitor dns resolver with native resolver#2432
MasterPtato wants to merge 1 commit into
05-07-fix_pegboard_fix_netns_path_bugfrom
05-07-fix_swap_status_monitor_dns_resolver_with_native_resolver

Conversation

@MasterPtato

Copy link
Copy Markdown
Contributor

Changes

MasterPtato commented May 7, 2025

Copy link
Copy Markdown
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This PR replaces the DNS resolver in the status monitor with the native system resolver, improving reliability by leveraging the system's built-in DNS resolution capabilities.

  • Modified packages/core/api/status/src/route/actor.rs to use ToSocketAddrs for native DNS resolution
  • Updated lookup_dns function to accept port parameter and run in a blocking task
  • Adapted test_actor_connection to pass port to lookup_dns for complete socket address resolution
  • Removed dependency on hickory_resolver in favor of system DNS resolver

1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines +321 to +330
// Use native resolver in a blocking task
let addrs = tokio::task::spawn_blocking(move || {
GlobalResult::Ok(
addr.to_socket_addrs()?
.into_iter()
.map(|x| x.ip())
.collect::<Vec<_>>(),
)
})
.await??;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logic: Double unwrap (??) of Result types could mask underlying errors. Consider handling each error case separately for better error reporting.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying rivet with  Cloudflare Pages  Cloudflare Pages

Latest commit: 13d14bb
Status: ✅  Deploy successful!
Preview URL: https://a51738b2.rivet.pages.dev
Branch Preview URL: https://05-07-fix-swap-status-monito.rivet.pages.dev

View logs

@MasterPtato MasterPtato force-pushed the 05-07-fix_swap_status_monitor_dns_resolver_with_native_resolver branch from 13d14bb to 35fc915 Compare May 9, 2025 23:59
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 9, 2025

Copy link
Copy Markdown

Deploying rivet-studio with  Cloudflare Pages  Cloudflare Pages

Latest commit: 35fc915
Status:⚡️  Build in progress...

View logs

@graphite-app

graphite-app Bot commented May 9, 2025

Copy link
Copy Markdown
Contributor

Merge activity

  • May 9, 7:59 PM EDT: MasterPtato added this pull request to the Graphite merge queue.
  • May 9, 8:00 PM EDT: CI is running for this pull request on a draft pull request (#2435) due to your merge queue CI optimization settings.
  • May 9, 8:01 PM EDT: Merged by the Graphite merge queue via draft PR: #2435.

graphite-app Bot pushed a commit that referenced this pull request May 10, 2025
<!-- Please make sure there is an issue that this PR is correlated to. -->

## Changes

<!-- If there are frontend changes, please include screenshots. -->
@graphite-app graphite-app Bot closed this May 10, 2025
@graphite-app graphite-app Bot deleted the 05-07-fix_swap_status_monitor_dns_resolver_with_native_resolver branch May 10, 2025 00:01
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.

2 participants