Files
firezone/rust/bin-shared/tests/network_notifiers.rs
Thomas Eizinger 48ba2869a8 chore(rust): ban the use of .unwrap except in tests (#7319)
Using the clippy lint `unwrap_used`, we can automatically lint against
all uses of `.unwrap()` on `Result` and `Option`. This turns up quite a
few results actually. In most cases, they are invariants that can't
actually be hit. For these, we change them to `Option`. In other cases,
they can actually be hit. For example, if the user supplies an invalid
log-filter.

Activating this lint ensures the compiler will yell at us every time we
use `.unwrap` to double-check whether we do indeed want to panic here.

Resolves: #7292.
2024-11-13 03:59:22 +00:00

46 lines
1.6 KiB
Rust

#![allow(clippy::unwrap_used)]
use firezone_bin_shared::{new_dns_notifier, new_network_notifier, platform::DnsControlMethod};
use futures::future::FutureExt as _;
use std::time::Duration;
use tokio::time::timeout;
/// Smoke test for the DNS and network change notifiers
///
/// Turn them on, wait a second, turn them off.
/// This tests that the threads quit gracefully when we call `close`, and they don't crash on startup.
#[tokio::test]
async fn notifiers() {
firezone_logging::test_global("debug");
let tokio_handle = tokio::runtime::Handle::current();
let mut dns = new_dns_notifier(tokio_handle.clone(), DnsControlMethod::default())
.await
.unwrap();
let mut net = new_network_notifier(tokio_handle, DnsControlMethod::default())
.await
.unwrap();
tokio::time::sleep(std::time::Duration::from_secs(1)).await;
// The notifiers always notify once they start listening for changes, to avoid gaps during startup.
timeout(Duration::from_secs(1), dns.notified())
.await
.unwrap()
.unwrap();
timeout(Duration::from_secs(1), net.notified())
.await
.unwrap()
.unwrap();
// After that first notification, we shouldn't get any other notifications during a normal unit test.
assert!(dns.notified().now_or_never().is_none());
assert!(net.notified().now_or_never().is_none());
// `close` consumes the notifiers, so we can catch errors and can't call any methods on a closed notifier. If the notifier is dropped, we internally call the same code that `close` calls.
dns.close().unwrap();
net.close().unwrap();
}