Devsy
Troubleshooting

Setup history

Devsy keeps redacted build and lifecycle output for workspace runs in a local store. Read it with devsy workspace logs --source setup or in the Logs tab of Devsy Desktop. For the commands, see Troubleshooting.

History exists only for runs that start after you install a release with this feature.

Retention and limits

BoundValue
Retained data per run, per store10 MiB
Retained data per workspace generation, per store50 MiB
Completed runs per workspace generation20
Retention age30 days
Total per store512 MiB

When a bound is reached, Devsy removes completed runs first. It never removes the segment an active run is writing.

When a run reaches its budget, Devsy stops storing output for that capture and keeps reading the command's output so the command does not block. The run is marked truncated, and the read response reports a capture gap with the affected producer and missing sequence range. A full budget does not change how a hook runs or its exit status.

Redaction

Devsy redacts output before it writes it to disk or sends it between machines.

Masked:

  • Known secret environment values.
  • Runtime and mount secrets.
  • Build secrets.
  • Credential patterns Devsy detects.

Not stored:

  • Environment snapshots.
  • Argument dumps of commands.
  • Resolved configuration that contains secrets.
  • Contents of secret files.

Devsy cannot detect every value a script invents or transforms. A script that prints a decoded or reformatted secret can leak it into history. Do not print secrets in lifecycle commands.

Availability

An unavailable history source returns a typed status in the response. The command does not fail.

  • A workspace whose agent is older than this feature, or whose runtime does not support read-only access, shows cached history only. Run devsy workspace logs without --source setup for container logs.
  • History is stored on the machine where the run happened. Devsy does not share it between machines.
  • Devsy writes output next to the process first, then copies it to the machine where you ran the command. If the remote copy is gone, for example because the container was destroyed, Devsy reports the records that were never copied as unavailable. If the local copy is also gone, the output cannot be recovered.
  • A response with complete=false and an availability reason is a successful read of partial history.

To fetch missing remote records, Devsy makes one read-only attempt with a five-second limit. It does not start, unpause, rebuild or install anything. If the workspace is stopped, you get the cached records and an availability note.

Interactive hooks

Output from a postStartCommand run with --interactive-post-start appears live in your terminal. Devsy does not store it in setup history, so devsy workspace logs --source setup does not show it. Devsy does not redact that live output, so a secret that the hook prints is visible on the terminal.

Desktop

Open the workspace and choose Logs.

  • The run selector lists retained runs. It opens the latest run first and keeps an older run you chose when a new operation starts.
  • The step list shows each build and lifecycle step with its command, time, outcome and capture condition.
  • A step is pending, deferred, running, succeeded, failed, skipped, canceled or completion unknown. The recorded reason and exit code appear when known. A step that succeeded with no output looks different from a step whose output was never captured.
  • A Running workspace does not mean every hook succeeded.
  • View logs on a failure notification, the workspace operation view or the creation wizard opens the failed run and, when Devsy can identify it, the failing step. Successful steps offer View output.
  • Output appears as literal text. Whitespace, blank lines and the stdout or stderr label are kept. Scroll up to pause auto-scroll.
  • A link to a run still works after a failed creation or a deletion removes the workspace. That view is read-only.
  • Use the export action to save a run.

Desktop diagnostic files are listed below the history. They are Desktop's own logs, and only the diagnostic log settings control them. Those settings do not turn off retained lifecycle output.

On this page