Class CannotWaitForObserverCompletion

Namespace

Cratis.Chronicle.Observation

Assembly

Cratis.Chronicle.dll

The exception that is thrown when observer completion is waited for on an append result that carries no observer surface.

public class CannotWaitForObserverCompletion : Exception, ISerializable

Inheritance

object

Exception

CannotWaitForObserverCompletion

Implements

ISerializable

Inherited Members

Exception.GetBaseException()

Exception.ToString()

Exception.GetType()

Exception.TargetSite

Exception.Message

Exception.Data

Exception.InnerException

Exception.HelpLink

Exception.Source

Exception.HResult

Exception.StackTrace

Exception.SerializeObjectState

object.MemberwiseClone()

object.Equals(object)

object.Equals(object, object)

object.ReferenceEquals(object, object)

object.GetHashCode()

Extension Methods

MethodCalls.CallGenericMethod<TOut, T>(T, Expression<Func<T, Func<TOut>>>, params Type[])

MethodCalls.CallGenericMethod<TOut, T, T1>(T, Expression<Func<T, Func<T1, TOut>>>, T1, params Type[])

MethodCalls.CallGenericMethod<TOut, T, T1, T2>(T, Expression<Func<T, Func<T1, T2, TOut>>>, T1, T2, params Type[])

MethodCalls.CallGenericMethod<TOut, T, T1, T2, T3>(T, Expression<Func<T, Func<T1, T2, T3, TOut>>>, T1, T2, T3, params Type[])

ConverterExtensions.ConvertTo(object, Type)

ConceptExtensions.GetConceptValue(object)

ConceptExtensions.IsConcept(object)

JsonValueExtensions.ToJsonValue(object?)

ObservableExtensions.InvokeAndWrapWithSubject<TResult>(object, Func<CancellationToken, IObservable<TResult>>)

ObservableExtensions.InvokeAndWrapWithTransformSubject<TResult, TSource>(object, Func<CancellationToken, IObservable<TSource>>, Func<TSource, TResult>)

Remarks

Waiting is only meaningful against a connection that actually has observers behind it. The in-process testing surfaces (EventScenario, EventStoreForTesting) run the event sequence without a silo, so no projection, reducer or reactor ever runs from an append there and there is nothing whose completion could be observed. Reporting success would let a spec assert that downstream work finished when none of it was ever started, so the wait fails by name instead - assert on the scenario's own surface, or move the spec to an out-of-process integration spec where observers genuinely run.

Constructors

CannotWaitForObserverCompletion(EventStoreName, EventSequenceId)

The exception that is thrown when observer completion is waited for on an append result that carries no observer surface.

public CannotWaitForObserverCompletion(EventStoreName eventStore, EventSequenceId eventSequenceId)

Parameters

eventStore EventStoreName

The EventStoreName the append targeted.

eventSequenceId EventSequenceId

The EventSequenceId the append targeted.

Remarks

Waiting is only meaningful against a connection that actually has observers behind it. The in-process testing surfaces (EventScenario, EventStoreForTesting) run the event sequence without a silo, so no projection, reducer or reactor ever runs from an append there and there is nothing whose completion could be observed. Reporting success would let a spec assert that downstream work finished when none of it was ever started, so the wait fails by name instead - assert on the scenario's own surface, or move the spec to an out-of-process integration spec where observers genuinely run.