not all errors are get correctly updates.

[smtmfft]

Describe the bug

For example, we get an error like this:

Description of the bug here.[2024-08-04T05:04:00Z INFO  risc0_driver::bonsai] Profiling enabled.
thread 'tokio-runtime-worker' panicked at provers/risc0/driver/src/bonsai.rs:268:20:
called `Result::unwrap()` on an `Err` value: No space left on device (os error 28)

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
             at /home/smtm/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.86/src/error.rs:565:25
   1: <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual
             at /rustc/becebb3158149a115cad8a402612e25436a7e37b/library/core/src/result.rs:1964:27
   2: risc0_zkvm::host::server::session::FileSegmentRef::new
             at /home/smtm/.cargo/registry/src/index.crates.io-6f17d22bba15001f/risc0-zkvm-1.0.1/src/host/server/session.rs:304:9
   3: risc0_zkvm::host::server::exec::executor::ExecutorImpl::run::{{closure}}
             at /home/smtm/.cargo/registry/src/index.crates.io-6f17d22bba15001f/risc0-zkvm-1.0.1/src/host/server/exec/executor.rs:115:54
   4: risc0_zkvm::host::server::exec::executor::ExecutorImpl::run_with_callback::{{closure}}

If we request same proof again,
it will give: {"data":{"status":"work_in_progress"},"status":"ok"}

It should either reports error or restart the proof generation depends on different errors.

Steps to reproduce

Steps to reproduce here.

Spam policy

• I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.