#[non_exhaustive]pub struct SessionLeaveFailureReason(pub String);Expand description
Current producer failure reasons for session/leaveCompleted;
receiver-open for additive future reasons.
Tuple Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.0: StringImplementations§
Source§impl SessionLeaveFailureReason
impl SessionLeaveFailureReason
Sourcepub const TIMEOUT: &'static str = "timeout"
pub const TIMEOUT: &'static str = "timeout"
timeout: the session did not finish shutting down within the leave’s
window. The host keeps the session.
Sourcepub const RESPONSE_UNDELIVERED: &'static str = "responseUndelivered"
pub const RESPONSE_UNDELIVERED: &'static str = "responseUndelivered"
responseUndelivered: the leave’s acceptance could not be delivered to
the client. The host keeps the session.
Sourcepub const PERSISTENCE_FAILED: &'static str = "persistenceFailed"
pub const PERSISTENCE_FAILED: &'static str = "persistenceFailed"
persistenceFailed: saving the session or releasing its writer lease
failed. The host keeps the session.
Sourcepub const RUNTIME_FAILED: &'static str = "runtimeFailed"
pub const RUNTIME_FAILED: &'static str = "runtimeFailed"
runtimeFailed: the session’s runtime failed while shutting down. The
host keeps the session.
Sourcepub const ABANDONED: &'static str = "abandoned"
pub const ABANDONED: &'static str = "abandoned"
abandoned: no host owns this leave’s result. A host that later took
the session’s writer recorded it because no result was recorded and
either the leave had reached its release point or the host that ran it
was proven dead; it never means the release failed. Recording it pushes
nothing; a client sees it only as the session/leaveCompleted
re-pushed after it sends the same leave command again.