Enum EnhanceApplicationError 

pub enum EnhanceApplicationError {
    Issue(IssueStoreError),
    Setting(EnhanceSettingStoreError),
    Bp(BlueprintStoreError),
    Log(EnhanceLogStoreError),
    Launch(TaskLaunchError),
    Serialize(Error),
    InvalidSemver {
        label: String,
        source: Error,
    },
    NoMatchingVersion {
        req: String,
    },
    Engine(EngineError),
    CommitShape(String),
    Clock(SystemTimeError),
    SpawnerAgentNotFound {
        name: String,
    },
    EpochCeilingExceeded {
        setting_id: String,
        ttl_secs: u64,
    },
    ZeroTtl {
        setting_id: String,
    },
}

Failure modes of EnhanceApplication::tick and the internal dispatch_one step it wraps.

Variants

Issue(IssueStoreError)

The IssueStore returned an error (enqueue, pop, or status update).

Setting(EnhanceSettingStoreError)

The EnhanceSettingStore returned an error while fetching the active setting.

Bp(BlueprintStoreError)

The BlueprintStore returned an error while resolving the orbit or target Blueprint.

Log(EnhanceLogStoreError)

The EnhanceLogStore returned an error while appending the outcome entry.

Launch(TaskLaunchError)

TaskLaunchService::launch failed after setup succeeded.

Serialize(Error)

Serializing the target Blueprint (or a directive derived from it) to JSON/YAML failed.

InvalidSemver

A stored version’s version_label is not valid semver.

Fields

label: String

The offending label string.

source: Error

The underlying semver parse error.

NoMatchingVersion

No stored version’s label satisfies the setting’s SemverReq.

Fields

req: String

The requirement string that matched nothing.

Engine(EngineError)

The engine reported an error (attach / dispatch).

CommitShape(String)

final_ctx.commit did not match the strict shape extract_commit expects, or the committer/store hashes disagreed.

Clock(SystemTimeError)

The system clock reported a time before the UNIX epoch while computing now_ms.

SpawnerAgentNotFound

The setting carries an EnhanceSetting::spawner override, but the orbit Blueprint declares no agent under the name the flow’s Step.ref points at. Fail loud: silently ignoring the override would run the Blueprint’s own spawner while the operator believes the swap took effect.

Fields

name: String

The agent name the override targets (= the flow Step.ref).

EpochCeilingExceeded

The drain stopped waiting on TaskLaunchService::launch after EnhanceSetting::ttl_secs and dropped it. Carries the number it blew through so the reason text an operator reads names the knob they can raise, not just the fact that something stopped.

Two facts the reason text has to carry, because an operator acts on it (see the ceiling block in dispatch_one for the evidence):

• Nothing was committed. That one is structural, not best-effort.
• Only the wait ended. A worker already running in an in-process lane keeps running — this ceiling bounds an Operator wait, and those lanes are not waits. So a re-post can put a second writer under the same project_root as the first, which is the one thing an operator must not do by reflex on reading “timed out”.

Fields

setting_id: String

The EnhanceSettingId whose ttl_secs bounded this epoch.

ttl_secs: u64

The ceiling in seconds, as declared by the setting.

ZeroTtl

EnhanceSetting::ttl_secs is 0.

Zero is refused rather than read as “no ceiling”. This repo has no zero-means-unbounded TTL: mse serve refuses worker_token_ttl_secs: 0 at startup and POST /v1/tasks rejects timeout_secs: 0 with a 400, both on the same ground — a zero TTL is a typo, not a policy. Inventing the sentinel here would recreate the exact defect this ceiling exists to remove: a field whose value does not mean what the field says it means.

The guard belongs one layer out, at POST /v1/enhance-settings, where it could be a 400 at write time instead of a rejected issue at dispatch time. It lives here because dispatch is the last place that can still refuse to run an epoch it would abort on its first poll.

Fields

setting_id: String

The EnhanceSettingId carrying the zero.

Trait Implementations

impl Debug for EnhanceApplicationError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for EnhanceApplicationError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for EnhanceApplicationError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<BlueprintStoreError> for EnhanceApplicationError

fn from(source: BlueprintStoreError) -> Self

Converts to this type from the input type.

impl From<EngineError> for EnhanceApplicationError

fn from(source: EngineError) -> Self

Converts to this type from the input type.

impl From<EnhanceLogStoreError> for EnhanceApplicationError

fn from(source: EnhanceLogStoreError) -> Self

Converts to this type from the input type.

impl From<EnhanceSettingStoreError> for EnhanceApplicationError

fn from(source: EnhanceSettingStoreError) -> Self

Converts to this type from the input type.

impl From<Error> for EnhanceApplicationError

fn from(source: Error) -> Self

Converts to this type from the input type.

impl From<IssueStoreError> for EnhanceApplicationError

fn from(source: IssueStoreError) -> Self

Converts to this type from the input type.

impl From<SystemTimeError> for EnhanceApplicationError

fn from(source: SystemTimeError) -> Self

Converts to this type from the input type.

impl From<TaskLaunchError> for EnhanceApplicationError

fn from(source: TaskLaunchError) -> Self

Converts to this type from the input type.