TODO(#16601) Make this method private once PerformUnlessClosing doesn't need it any more

Timestamp of the latest known state of traffic purchased entries.

Optional subscriber to the traffic control processor, only used for the new top up implementation

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

Return the latest known traffic states for the requested members, or all currently cached members if requestedMembers is empty.

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

Set this to true to get detailed information about all futures that did not complete during shutdown.

Returns the latest known balance for the given member.

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

Prunes traffic control data such as it can still be queried up to 'upToExclusive'.

Create a traffic state for a new member at the given timestamp. Its base traffic remainder will be equal to the max burst window configured at that point in time.

TODO(#16601) Make this method private once PerformUnlessClosing doesn't need it any more

This method must be called during the crash recovery and must reset the state of rate limit manager to the state at the given timestamp (stores + internal state if there is i.e. a cache).

Schedules the given task to be run upon closing.

Register a task to run when closing is initiated, or run it immediately if closing is already ongoing. Unlike runOnClose, this method does not guarantee that this task will have run by the time the LifeCycleManager's closeAsync method completes or AutoCloseable's close returns. This is because the task is run immediately if the component has already been closed.

Variant of runOnOrAfterClose that does not return a com.digitalasset.canton.lifecycle.LifeCycleRegistrationHandle.

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has completed (as defined by the com.digitalasset.canton.util.Thereafter instance) or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Convenience method for synchronizing on Futures instead of FutureUnlessShutdowns. Equivalent to

synchronizeWithClosing(name)(FutureUnlessShutdown.outcomeF(f))

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has finished or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has completed (as defined by the com.digitalasset.canton.util.Thereafter instance) or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Runs the computation fa unless isClosing returns true.

This method does not delay the closing while fa is running, unlike the methods in HasSynchronizeWithClosing. Accordingly, this method is useful for intermittent checks whether the result of the computation is still relevant.

Validate submission requests after they've been sequenced. The same validation as performed at submission is run again, to ensure that the submitting sequencer was not malicious. If the request is valid, the cost is consumed. This method MUST be called sequentially for a given sender, meaning concurrent updates are not supported. This method MUST be called in order of sequencing times, meaning 2 events sequenced at T1 and T2 such that T2 > T1 must be processed by this method in the order T1 -> T2. However, if T1 and T2 have been processed in the correct order, it is then ok to call the method with T1 again, which will result in the same output as when it was first called.

Validate signed submission requests received by the sequencer. Requests with a an invalid cost or a cost that exceeds the traffic credit will be rejected.