BigPizzaV3/CodexPlusPlus · error · anyhow::Error

export markdown task failed: {error}

Error message

export markdown task failed: {error}

What it means

Wrapped failure thrown by LauncherDataService::export_markdown when the spawn_blocking task around export_markdown_from_paths fails at the task level (JoinError), formatted as "export markdown task failed: {error}". The URL/route handler surfaces it; domain errors from the export itself take a different path.

Source

Thrown at apps/codex-plus-launcher/src/main.rs:648

        })
        .await
        .map_err(|error| anyhow::anyhow!("delete task failed: {error}"))
    }

    async fn undo(&self, undo_token: String) -> anyhow::Result<DeleteResult> {
        let adapter = self.storage_adapter();
        tokio::task::spawn_blocking(move || adapter.undo(&undo_token))
            .await
            .map_err(|error| anyhow::anyhow!("undo task failed: {error}"))
    }

    async fn export_markdown(&self, session: SessionRef) -> anyhow::Result<ExportResult> {
        let db_paths = self.candidate_db_paths();
        tokio::task::spawn_blocking(move || {
            codex_plus_data::export_markdown_from_paths(db_paths, &session)
        })
        .await
        .map_err(|error| anyhow::anyhow!("export markdown task failed: {error}"))
    }

    async fn thread_usage_history(&self, session: SessionRef) -> anyhow::Result<Value> {
        let adapter = self.storage_adapter();
        tokio::task::spawn_blocking(move || adapter.codex_thread_usage_history(&session))
            .await
            .map_err(|error| anyhow::anyhow!("thread usage history task failed: {error}"))
    }

    async fn find_archived_thread_by_title(
        &self,
        title: String,
    ) -> anyhow::Result<Option<SessionRef>> {
        let adapter = self.storage_adapter();
        tokio::task::spawn_blocking(move || adapter.find_archived_thread_by_title(&title))
            .await
            .map_err(|error| anyhow::anyhow!("archived lookup task failed: {error}"))
    }

View on GitHub (pinned to f2074595a2)

Solutions

1. 查看导出任务的 panic 日志定位崩溃点
2. 确认候选数据库路径均有效可读
3. 重试导出
4. 修复 export_markdown_from_paths 内的 unwrap/越界路径

When it happens

Trigger: Thrown at apps/codex-plus-launcher/src/main.rs:648 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of BigPizzaV3/CodexPlusPlus@f2074595a2 (2026-08-23). Data as JSON: /api/errors/55d55ffbcdf84eb5. Report an issue: GitHub.