Cancels a pending send without notifying any callers of the result. Should only be used if the send operation itself fails and the transport returns an error indicating that the send will never be sequenced. The SequencerClient should then call cancel to immediately allow retries with the same message-id and then propagate the send error to the caller.

Blocks until all earlier tasks have completed and then prevents further tasks from being run.

closeAsync asynchronously releases resources held by a future

Check whether we're closing. Susceptible to race conditions; unless you're using using this as a flag to the retry lib or you really know what you're doing, prefer performUnlessClosing and friends.

track running futures on shutdown

set to true to get detailed information about all futures that did not complete during shutdown. if set to false, we don't do anything.

Performs the task given by f unless a shutdown has been initiated. The shutdown will only begin after f completes, but other tasks may execute concurrently with f, if started using this function, or one of the other variants (performUnlessClosingF and performUnlessClosingEitherT). The tasks are assumed to take less than closingTimeout to complete.

DO NOT CALL this.close as part of f, because it will result in a deadlock.

Performs the EitherT[Future] given by etf unless a shutdown has been initiated, in which case the provided error is returned instead. Both etf and the error are lazy; etf is only evaluated if there is no shutdown, the error only if we're shutting down. The shutdown will only begin after etf completes, but other tasks may execute concurrently with etf, if started using this function, or one of the other variants (performUnlessClosing and performUnlessClosingF). The tasks are assumed to take less than closingTimeout to complete.

DO NOT CALL this.close as part of etf, because it will result in a deadlock.

Performs the Future given by f unless a shutdown has been initiated. The future is lazy and not evaluated during shutdown. The shutdown will only begin after f completes, but other tasks may execute concurrently with f, if started using this function, or one of the other variants (performUnlessClosing and performUnlessClosingEitherT). The tasks are assumed to take less than closingTimeout to complete.

DO NOT CALL this.close as part of f, because it will result in a deadlock.

Register a task to run when shutdown is initiated.

You can use this for example to register tasks that cancel long-running computations, whose termination you can then wait for in "closeAsync".

Provide the latest sequenced event to update the send tracker and notify the handler of any sends that have timed out due to the new sequencing time. Callers must not call this concurrently and it is assumed that it is called with sequenced events in order of sequencing. On receiving an event it will perform the following steps in order:

1. If the event is a Deliver or DeliverError from a send that is being tracked it will stop tracking this message id. This allows using the message-id for new sends. 2. Checks for any pending sends that have a max-sequencing-time that is less than the timestamp of this event. These events have timed out and a correct sequencer implementation will no longer sequence any events for this send. The provided timeout handler will be called with the timed out message id. If multiple sends are timed out the handler will be called sequentially with each message id (note there is currently no defined order for the message ids it will receive). If the handler fails the update method will immediately return and any subsequent timed out message ids will not be provided to the handler.

The operations performed by update are not atomic, if an error is encountered midway through processing an event then a subsequent replay will cause operations that still have pending sends stored to be retried.