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

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

The order in which the subscriber should be executed among all the subscriptions. Lower values are executed first.

synchronizer generates nonce that he expects the participant to use to concatenate with the synchronizer's id and sign to proceed with the authentication (step 2). We expect to find a key with usage 'SequencerAuthentication' to sign these messages.

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.

synchronizer topology client subscriber used to remove member tokens if they get disabled

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

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

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.

Move the highest known (effective / approximate) timestamp ahead in the future.

May only be called if:

1. All committed topology transactions with effective time up to effectiveTimestamp have been persisted in the topology store.
2. All committed topology transactions with sequenced time up to sequencedTimestamp have been persisted in the topology store.
3. If this method is called with potentialTopologyChange == true, then for every subsequent committed topology transaction either updateHead(potentialTopologyChange == true, ...) or observed must be called again; such calls must occur with ascending effective timestamps.
4. sequencedTimestamp <= effectiveTimestamp
5. approximateTimestamp <= effectiveTimestamp
6. A sequenced event with timestamp at least approximateTimestamp has been received from the sequencer.

synchronizer checks that the signature given by the member matches and returns a token if it does (step 4)

synchronizer checks if the token given by the participant is the one previously assigned to it for authentication. The participant also provides the synchronizer id for which they think they are connecting to. If this id does not match this synchronizer's id, it means the participant was previously connected to a different synchronizer on the same address and now should be informed that this address now hosts a different synchronizer.