fix: resolve /a0 display paths outside docker and tolerate a missing display root #115
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/a0-symbolics!115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dev-path-display-mapping"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What changed
helpers/files.fix_dev_pathconverts/a0/...display paths to base-dir-relative paths whenever the runtime is not dockerized (previously only in development mode).usr/workdirwhen the resolved workdir lies outside the runtime base dir (display root unavailable).Why
CI environments run the framework without the docker
/a0mount and are neither dockerized nor in development mode.workdir_pathdefaults to the/a0/usr/workdirdisplay path, so prompt-rendering tests crashed withPermissionError: /a0(observed on the host nix runner in #51's focused job).Real docker behavior is unchanged: inside docker
is_dockerized()is true and/a0is the base dir.Verification
nix develop --command python -m pytest -q tests/test_default_prompt_budget.pypasses on a host without/a0(12 passed); it failed on all 5 parametrizations before.Related: #51