Files
codex/codex-rs/app-server/src/request_processors/rollout.rs
T
jif 821ad43f9d Tag rollout compression metrics by trigger (#46047)
## Why

Compression metrics do not distinguish startup runs from runs requested through
`rollout/compress`, making their outcomes indistinguishable by entry point.

## What changed

Pass `RolloutCompressionTrigger` from startup and RPC callers through the
compression worker. Add a `trigger` tag with `startup` or `rpc` to run, file,
scan-error, and temporary-file cleanup metrics, including durations, byte counts,
and compression ratios.

GitOrigin-RevId: f23d9da791b666a7311f2323f6bead6570067798
2026-09-16 22:33:15 +00:00

25 lines
927 B
Rust

//! Triggers local rollout maintenance without waiting for the background pass.
use super::ThreadRequestProcessor;
use super::thread_processor::unsupported_thread_store_operation;
use codex_app_server_protocol::ClientResponsePayload;
use codex_app_server_protocol::JSONRPCErrorError;
use codex_app_server_protocol::RolloutCompressResponse;
use codex_thread_store::LocalThreadStore;
impl ThreadRequestProcessor {
pub(crate) fn rollout_compress(
&self,
) -> Result<Option<ClientResponsePayload>, JSONRPCErrorError> {
if !self.thread_store.as_any().is::<LocalThreadStore>() {
return Err(unsupported_thread_store_operation("rollout/compress"));
}
codex_rollout::spawn_rollout_compression_worker(
self.config.codex_home.to_path_buf(),
codex_rollout::RolloutCompressionTrigger::Rpc,
);
Ok(Some(RolloutCompressResponse {}.into()))
}
}