endpoint-libs 3.2.1

use std::pin::pin;
use std::sync::atomic::{AtomicBool, Ordering};

use nagoya::reactor::Handle;
use nagoya::signal::{Signal, SignalKind};
use nagoya::sync::Notify;

/// A flag every waiter observes, including one that arrives after the cancel.
///
/// `Notify::notify_waiters` wakes the current set and leaves no permit. That
/// is nagoya `sync.rs`, on the 0.1.11 this crate pins. A waiter that
/// starts later reads [`Shutdown::is_cancelled`] instead of taking a stored
/// wake, which is the half `CancellationToken::cancel` was providing.
pub struct Shutdown {
    cancelled: AtomicBool,
    notify: Notify,
}

impl Default for Shutdown {
    fn default() -> Self {
        Self::new()
    }
}

impl Shutdown {
    /// A flag that has not been cancelled.
    #[must_use]
    pub const fn new() -> Self {
        Self {
            cancelled: AtomicBool::new(false),
            notify: Notify::new(),
        }
    }

    /// Store the flag, then wake everyone currently waiting.
    ///
    /// The store comes first. A waiter that observes the broadcast and then
    /// reads the flag has to see `true`, and `notify_waiters` keeps no permit
    /// that could cover the other order.
    pub fn cancel(&self) {
        self.cancelled.store(true, Ordering::Release);
        self.notify.notify_waiters();
    }

    /// Whether [`Shutdown::cancel`] has run.
    #[must_use]
    pub fn is_cancelled(&self) -> bool {
        self.cancelled.load(Ordering::Acquire)
    }

    /// Resolves once [`Shutdown::cancel`] has run.
    ///
    /// The wait is registered before the flag is read. A cancel landing
    /// between the two would otherwise be lost, because the broadcast keeps
    /// no permit. This is the same order nagoya's `Barrier` uses.
    pub async fn cancelled(&self) {
        loop {
            let notified = self.notify.notified();
            let mut notified = pin!(notified);
            if notified.as_mut().enable() {
                if self.is_cancelled() {
                    return;
                }
                continue;
            }
            if self.is_cancelled() {
                return;
            }
            notified.await;
        }
    }
}

/// Process-wide shutdown flag. Delivery of the unix signals is
/// [`nagoya::signal::Signal`]; this is only the flag those waits set.
pub static CANCELLATION_TOKEN: Shutdown = Shutdown::new();

/// Initialize and return the signals (sigterm, sigint), bound to `handle`.
///
/// **Breaking change.** This used to take nothing and return
/// `tokio::signal::unix::Signal`. tokio's `signal()` reached a process-wide
/// driver that the runtime was already turning, so the caller had nothing to
/// say; a nagoya [`Signal`] is registered on one reactor and its
/// [`recv`](Signal::recv) completes only while *that* reactor is being polled.
/// The reactor is therefore a parameter rather than an assumption, and the
/// caller has to guarantee two things for the wait to ever finish: that
/// `handle` names the reactor the returned values are awaited on, and that
/// something keeps polling it. A signal delivered while nobody polls that
/// reactor is not lost, because it stays readable on the descriptor, but
/// nothing observes it until the polling resumes.
///
/// There is one waiter per signal number for the whole process. A second call
/// made before the first pair is dropped fails with `EBUSY`, which is also why
/// [`signal_received_silent`] and this cannot both be live at once.
pub fn init_signals(handle: &Handle) -> eyre::Result<(Signal, Signal)> {
    let sigterm = Signal::new(SignalKind::terminate(), handle)?;
    let sigint = Signal::new(SignalKind::interrupt(), handle)?;
    Ok((sigterm, sigint))
}

/// Wait for either signal and log the one that arrived.
///
/// The signature is unchanged apart from [`Signal`] now being nagoya's, so the
/// reactor requirement rides along with the values [`init_signals`] handed
/// back rather than being restated here.
pub async fn wait_for_signals(sigterm: &mut Signal, sigint: &mut Signal) {
    // SIGTERM is polled first. Both arms set the same flag; the name in the log
    // is the only difference, and a pending SIGTERM is the one we report.
    let term = sigterm.recv();
    let int = sigint.recv();
    futures::pin_mut!(term, int);
    // `recv` now resolves to a `Result`, and the error is discarded on purpose:
    // a descriptor that has failed will not deliver a signal either, so the
    // only honest answer left is to shut down, which is what both arms do.
    match futures::future::select(term, int).await {
        futures::future::Either::Left(_) => inform_terminate("SIGTERM"),
        futures::future::Either::Right(_) => inform_terminate("SIGINT"),
    }
}

/// Wait for either signal without logging or setting the flag.
///
/// **Breaking change**, for the two reasons [`init_signals`] gives: it needs a
/// `handle` for the same reactor it is awaited on, and creating the waiters can
/// now fail, so the failure is returned instead of being swallowed by an
/// `expect("")`. `EBUSY` here is not hypothetical: it is what this returns
/// whenever [`init_signals`] already holds SIGTERM and SIGINT, which in this
/// crate is the ordinary case.
pub async fn signal_received_silent(handle: &Handle) -> eyre::Result<()> {
    let (mut sigterm, mut sigint) = init_signals(handle)?;
    let term = sigterm.recv();
    let int = sigint.recv();
    futures::pin_mut!(term, int);
    let _ = futures::future::select(term, int).await;
    Ok(())
}

/// print external signal
fn inform_terminate(signal_alias: &str) {
    if !get_terminate_flag() {
        tracing::warn!("received {signal_alias} signal, terminating program");
        set_terminate_flag()
    }
}

pub fn set_terminate_flag() {
    CANCELLATION_TOKEN.cancel();
}

pub fn get_terminate_flag() -> bool {
    CANCELLATION_TOKEN.is_cancelled()
}

#[cfg(test)]
mod tests {
    use std::future::Future;
    use std::task::Context;

    use super::*;

    #[test]
    fn cancel_completes_a_waiter_that_already_parked() {
        let shutdown = Shutdown::new();
        let mut fut = pin!(shutdown.cancelled());
        let waker = futures::task::noop_waker();
        let mut cx = Context::from_waker(&waker);
        assert!(fut.as_mut().poll(&mut cx).is_pending());
        assert!(!shutdown.is_cancelled());

        shutdown.cancel();

        assert!(shutdown.is_cancelled());
        assert!(fut.as_mut().poll(&mut cx).is_ready());
    }

    #[test]
    fn a_waiter_that_starts_after_cancel_completes_immediately() {
        let shutdown = Shutdown::new();
        shutdown.cancel();

        let mut fut = pin!(shutdown.cancelled());
        let waker = futures::task::noop_waker();
        let mut cx = Context::from_waker(&waker);
        assert!(shutdown.is_cancelled());
        assert!(fut.as_mut().poll(&mut cx).is_ready());
    }
}