//! The stream reactor.

use crate::circuit::circhop::CircHopOutbound;

use crate::circuit::reactor::macros::derive_deftly_template_CircuitReactor;

use crate::circuit::{CircHopSyncView, UniqId};

use crate::congestion::{CongestionControl, sendme};

use crate::memquota::{CircuitAccount, SpecificAccount as _, StreamAccount};

use crate::stream::CloseStreamBehavior;

use crate::stream::cmdcheck::StreamStatus;

use crate::stream::flow_ctrl::state::WithSidechannelMitigations;

use crate::streammap;

use crate::util::err::ReactorError;

use crate::{Error, HopNum};

#[cfg(any(feature = "hs-service", feature = "relay"))]

use crate::stream::incoming::{

    InboundDataCmdChecker, IncomingStreamRequest, IncomingStreamRequestContext,

    IncomingStreamRequestDisposition, IncomingStreamRequestHandler, StreamReqInfo,

};

use tor_async_utils::{SinkTrySend as _, SinkTrySendError as _};

use tor_cell::chancell::CircId;

use tor_cell::relaycell::msg::{AnyRelayMsg, Begin, BeginDir, End, EndReason, Resolve};

use tor_cell::relaycell::{

    AnyRelayMsgOuter, RelayCellFormat, RelayCmd, StreamId, UnparsedRelayMsg,

};

use tor_error::{internal, into_internal};

use tor_log_ratelim::log_ratelim;

use tor_rtcompat::{DynTimeProvider, Runtime, SleepProvider as _};

use derive_deftly::Deftly;

use futures::SinkExt;

use futures::channel::mpsc;

use futures::{FutureExt as _, StreamExt as _, future, select_biased};

use tracing::debug;

use std::pin::Pin;

use std::result::Result as StdResult;

use std::sync::{Arc, Mutex};

use std::task::Poll;

use std::time::Duration;

/// Trait for customizing the behavior of the stream reactor.

///

/// Used for plugging in the implementation-dependent (client vs relay)

/// parts of the implementation into the generic one.

pub(crate) trait StreamHandler: Send + Sync + 'static {

    /// Return the amount of time a newly closed stream

    /// should be kept in the stream map for.

    ///

    /// This is the amount of time we are willing to wait for

    /// an END ack before removing the half-stream from the map.

    fn halfstream_expiry(&self, hop: &CircHopOutbound) -> Duration;

    /// Whether sidechannel mitigations should be enabled for incoming streams.

    fn flowctrl_sidechannel_mitigations(&self) -> WithSidechannelMitigations;

}

/// The stream reactor for a given hop.

///

/// Drives the application streams.

///

/// This reactor accepts [`CtrlMsg`]s from the forward reactor over its [`Self::cell_rx`]

/// MPSC channel, and delivers them to the corresponding stream entries in the stream map.

///

/// The local streams are polled from the main loop, and any ready messages are sent

/// to the backward reactor over the `bwd_tx` MPSC channel for packaging and delivery.

///

/// Shuts downs down if an error occurs, or if the sending end

/// of the `cell_rx` MPSC channel, i.e. the forward reactor, closes.

#[derive(Deftly)]

#[derive_deftly(CircuitReactor)]

#[deftly(reactor_name = "stream reactor")]

#[deftly(run_inner_fn = "Self::run_once")]

#[must_use = "If you don't call run() on a reactor, the circuit won't work."]

pub(crate) struct StreamReactor {

    /// The hop this stream reactor is for.

    ///

    /// This is `None` for relays.

    hopnum: Option<HopNum>,

    /// The state of this circuit hop.

    hop: CircHopOutbound,

    /// The time provider.

    time_provider: DynTimeProvider,

    /// An identifier for logging about this reactor's circuit.

    unique_id: UniqId,

    /// The circuit identifier on the inbound Tor channel.

    circ_id: CircId,

    /// Receiver for Tor stream data that need to be delivered to a Tor stream.

    ///

    /// The sender is in the [`HopMgr`](super::hop_mgr::HopMgr) of the

    /// [`ForwardReactor`](super::ForwardReactor), which will forward all cells

    /// carrying Tor stream data to us.

    ///

    /// This serves a dual purpose:

    ///

    ///   * it enables the `ForwardReactor` to deliver Tor stream data received from the client

    ///   * it lets the `StreamReactor` know if the `ForwardReactor` has shut down:

    ///     we select! on this MPSC channel in the main loop, so if the `ForwardReactor`

    ///     shuts down, we will get EOS upon calling `.next()`)

    cell_rx: mpsc::Receiver<CtrlMsg>,

    /// Sender for sending Tor stream data to [`BackwardReactor`](super::BackwardReactor).

    bwd_tx: mpsc::Sender<ReadyStreamMsg>,

    /// A handler for incoming streams.

    ///

    /// Set to `None` if incoming streams are not allowed on this circuit.

    ///

    /// This handler is shared with the [`HopMgr`](super::hop_mgr::HopMgr) of this reactor,

    /// which can install a new handler at runtime (for example, in response to a CtrlMsg).

    /// The ability to update the handler after the reactor is launched is needed

    /// for onion services, where the incoming stream request handler only gets installed

    /// after the virtual hop is created.

    #[cfg(any(feature = "hs-service", feature = "relay"))]

    incoming: Arc<Mutex<Option<IncomingStreamRequestHandler>>>,

    /// A handler for customizing the stream reactor behavior.

    inner: Arc<dyn StreamHandler>,

    /// Memory quota account

    memquota: CircuitAccount,

}

#[allow(unused)] // TODO(relay)

impl StreamReactor {

    /// Create a new [`StreamReactor`].

    #[allow(clippy::too_many_arguments)] // TODO

    /// Helper for [`run`](Self::run).

    ///

    /// Polls the stream map for messages

    /// that need to be delivered to the other endpoint,

    /// and the `cells_rx` MPSC stream for stream messages received

    /// from the `ForwardReactor` that need to be delivered to the application streams.

        use postage::prelude::{Sink as _, Stream as _};

        // Garbage-collect all halfstreams that have expired.

        //

        // Note: this will iterate over the closed streams of this hop.

        // If we think this will cause perf issues, one idea would be to make

        // StreamMap::closed_streams into a min-heap, and add a branch to the

        // select_biased! below to sleep until the first expiry is due

        // (but my gut feeling is that iterating is cheaper)

                // We can't send anything on this hop that counts towards SENDME windows.

                //

                // Note: this does not block outgoing flow-control messages:

                //

                //   * circuit SENDMEs are initiated by the forward reactor,

                //     by sending a BackwardReactorCmd::SendRelayMsg to BWD,

                //   * stream SENDMEs will be initiated by StreamTarget::send_sendme(),

                //     by sending a control message to the reactor

                //     (TODO(relay): not yet implemented)

                //   * XOFFs are sent in response to messages on streams

                //     (i.e. RELAY messages with non-zero stream IDs).

                //     These messages are delivered to us by the forward reactor

                //     inside BackwardReactorCmd::HandleMsg

                //   * XON will be initiated by StreamTarget::drain_rate_update(),

                //     by sending a control message to the reactor

                //     (TODO(relay): not yet implemented)\

                // No ready streams

                //

                // TODO(flushing): if there are no ready Tor streams, we might want to defer

                // flushing until stream data becomes available (or until a timeout elapses).

                // The deferred flushing approach should enable us to send

                // more than one message at a time to the channel reactor.

            };

                // This means the local sender has been dropped,

                // which presumably can only happen if an error occurs,

                // or if the Tor stream ends. In both cases, we're going to

                // want to send an END to the client to let them know,

                // and to remove the stream from the stream map.

                //

                // TODO(relay): the local sender part is not implemented yet

                    // The forward reactor has shut down

                };

            }

            }

        }

    /// Handle a stream message sent to us by the forward reactor.

    ///

    /// Delivers the message to its corresponding application stream.

            CtrlMsg::DeliverStreamMsg {

            } => {

            }

            #[cfg(any(feature = "hs-service", feature = "relay"))]

            }

        }

    /// Deliver `msg` to the specified stream

        // We need to apply stream-level flow control *before* encoding the message.

        // May optionally return a message that needs to be sent back to the client.

        // TODO(DEDUP): this contains parts of Circuit::send_relay_cell_inner()

            // We might be out of capacity entirely; see if we are about to hit a limit.

            //

            // TODO: If we ever add a notion of _recoverable_ errors below, we'll

            // need a way to restore this limit, and similarly for about_to_send().

            // We need to apply stream-level flow control *before* encoding the message

            // (the BWD handles the encoding)

            // NOTE: on the client side, we call note_data_sent()

            // just before writing the cell to the channel.

            // We can't do that here, because we're not the ones

            // encoding the cell, so we don't have the SENDME tag

            // which is needed for note_data_sent().

            //

            // Instead, we notify the CC algorithm in the BWD,

            // right after we've finished sending the cell.

    /// Handle a RELAY message that has a non-zero stream ID.

    ///

    /// A returned message is one that we need to send back to the client.

    //

    // TODO(relay): this is very similar to the client impl from

    // Circuit::handle_in_order_relay_msg()

        // Check if any of our already-open streams want this message

        // If it was an incoming stream request, we don't need to worry about

        // sending an XOFF as there's no stream data within this message.

            cfg_if::cfg_if! {

                if #[cfg(any(feature = "hs-service", feature = "relay"))] {

                } else {

                    return Err(

                        Error::CircProto(format!("Cannot handle {} cells on this circuit", msg.cmd())).into(),

                    );

                }

            }

        // We may want to send an XOFF if the incoming buffer is too large.

    /// A helper for handling incoming stream requests.

    ///

    /// Accepts the specified incoming stream request,

    /// by adding a new entry to our stream map.

    ///

    /// Returns the cell we need to send back to the client,

    /// if an error occurred and the stream cannot be opened.

    ///

    /// Returns None if everything went well

    /// (the CONNECTED response only comes if the external

    /// consumer of our [Stream](futures::Stream) of incoming Tor streams

    /// is able to actually establish the connection to the address

    /// specified in the BEGIN).

    ///

    /// Any error returned from this function will shut down the reactor.

    #[cfg(any(feature = "hs-service", feature = "relay"))]

        };

            };

            };

            // We can't honor this request, so we bail by sending an END.

                // The IncomingStreamRequestHandler's stream is full; it isn't

                // handling requests fast enough. So instead, we reply with an

                // END cell.

                );

                // The IncomingStreamRequestHandler's stream has been dropped.

                // In the Tor protocol as it stands, this always means that the

                // circuit itself is out-of-use and should be closed.

                //

                // Note that we will _not_ reach this point immediately after

                // the IncomingStreamRequestHandler is dropped; we won't hit it

                // until we next get an incoming request.  Thus, if we later

                // want to add early detection for a dropped

                // IncomingStreamRequestHandler, we need to do it elsewhere, in

                // a different way.

                    circ_uniq_id = %self.unique_id,

                    backward_circ_id = %self.circ_id,

                    "Incoming stream request receiver dropped",

                );

                // This will _cause_ the circuit to get closed.

            } else {

                // There are no errors like this with the current design of

                // futures::mpsc, but we shouldn't just ignore the possibility

                // that they'll be added later.

            }

    /// Check if we should reject this incoming stream request or not.

    ///

    /// Returns a cell we need to send back to the client if we must reject the request,

    /// or `None` if we are allowed to accept it.

    ///`

    /// Any error returned from this function will shut down the reactor.

    #[cfg(any(feature = "hs-service", feature = "relay"))]

        use IncomingStreamRequestDisposition::*;

        // Run the externally provided filter to check if we should

        // open the stream or not.

            Accept => {

                // All is well, we can accept the stream request

            }

            }

        }

    /// Handle a [`StreamEvent`].

            }

            }

        }

    /// Close the stream that has the specified `sid`.

    ///

    /// The `behav` controls whether an `END` will be sent or not.

    ///

    /// This calls [`CircHopOutbound::close_stream`] under the hood,

    /// which removes the stream from the stream map,

    /// and returns an optional `END` cell to send back to the other party.

            // We may not need to send anything at all...

        };

    /// Wrap `msg` in [`ReadyStreamMsg`], and send it to the backward reactor.

}

/// A Tor stream-related event.

enum StreamEvent {

    /// An application stream was closed.

    ///

    /// The corresponding entry needs to be removed from the reactor's stream map.

    ApplicationStreamClosed(StreamId),

    /// A stream has a ready message.

    ReadyMsg {

        /// The ID of the stream to close.

        sid: StreamId,

        /// The message.

        msg: AnyRelayMsg,

    },

}

/// Convert an incoming stream request message (BEGIN, BEGIN_DIR, RESOLVE, etc.)

/// to an [`IncomingStreamRequest`]

///

// TODO(dedup): when we rewrite the client reactor in the multi-reactor register,

// we should rethink this part a bit: ideally, onion services shouldn't even

// try to parse BEGIN_DIR, RESOLVE.

//

// We will likely need an implementation-specific hook for this,

// similar to the `{Forward,Backward}Handler` implementation-specific handlers

// we have for the FWD and BWD reactors.

//

// See https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4188#note_3432579

#[cfg(any(feature = "hs-service", feature = "relay"))]

    /// Helper for parsing an incoming stream request

    /// (BEGIN, BEGIN_DIR, or RESOLVE)

    macro_rules! parse_stream_req {

        ($msg:expr, $type:tt) => {{

            let req = $msg

                .decode::<$type>()

                .into_msg();

            IncomingStreamRequest::$type(req)

        }};

    }

            // It's a bug if we reach this point, because CircHopOutbound::handle_msg()

            // should have consumed the message (by forwarding it to the appropriate stream

            // in its stream map)

        }

    };

/// A stream message to be sent to the backward reactor for delivery.

pub(crate) struct ReadyStreamMsg {

    /// The hop number, or `None` if we are a relay.

    pub(crate) hop: Option<HopNum>,

    /// The message to send.

    pub(crate) msg: AnyRelayMsgOuter,

    /// The cell format used with the hop the message should be sent to.

    pub(crate) relay_cell_format: RelayCellFormat,

    /// The CC object to use.

    pub(crate) ccontrol: Arc<Mutex<CongestionControl>>,

}

/// A control message

/// that needs to be handled by [`StreamReactor`].

pub(crate) enum CtrlMsg {

    /// Stream data received from the other endpoint

    /// that needs to be delivered to a Tor stream

    DeliverStreamMsg {

        /// The ID of the stream this message is for.

        sid: StreamId,

        /// The message.

        msg: UnparsedRelayMsg,

        /// Whether the cell this message came from counts towards flow-control windows.

        cell_counts_toward_windows: bool,

    },

    /// Close the specified pending incoming stream, sending the provided END message.

    #[cfg(any(feature = "hs-service", feature = "relay"))]

    ClosePendingStream {

        /// The stream ID to send the END for.

        stream_id: StreamId,

        /// The END message to send, if any.

        behav: CloseStreamBehavior,

    },

}