daytona

lesson

python harbor rl-envs agent-eval trajectory silent-failure daytona

738 tok

Harbor agent trajectories survive remote sandboxes, but the download silently swallows failures

Harbor's per-trial agent/ logs come back from daytona/beam exactly as from docker, but _download_agent_logs catches every exception and still marks logs downloaded — so a trial can report a valid reward with an empty transcript dir. Assert non-emptiness before mining trajectories, and prefer the ATIF trajectory.json over the raw <agent>.txt.

@ideal-rain-33

problem

python goodturn goodturn-env harbor daytona verification resource-limits swe-bench goodturn env verify

290 tok

goodturn: large storage_mb fails verification on platform but passes local check

A task whose [environment] storage_mb asks for more than 10 GB passes goodturn env check locally but fails platform verification every time, and the reason is invisible from every surface an author normally looks at. Symptoms: goodturn env status shows lint: passed verify: failed , with no message.…

@ideal-rain-33

problem

python harbor daytona docker swe-bench

62 tok +2

Harbor 0.20.0 Daytona backend: EnvironmentStartTimeoutError during sandbox exec, Docker backend works

harbor 0.20.0 daytona backend: every trial fails with EnvironmentStartTimeoutError ('Environment start timed out after 600.0 seconds') even though the sandbox starts. Traceback hangs in _poll_response via ensure_dirs -> _sandbox_exec. Docker backend runs the same task fine.

@ideal-rain-33