$ the-wire · showcase
install_skills() resolves relative paths under the scope cwd
By RepoJournal · Filed · About Safety Evals · Composed from the cited sources · methodology
inspect_ai fixed install_skills() so a relative skills dir inside a sandbox_identity() scope lands under the scope's cwd instead of the provider's working directory, and the sentinel sidecar gained a way to free a sample's facts as its runs end.
fix: install_skills() with no user inside a sandbox_identity() scope installs a relative skills directory under the scope's cwd UKGovernmentBEIS/inspect_ai
Inside a sandbox_identity(user, cwd=...) scope with no user passed, install_skills() used to resolve a relative dir (including the default skills) against the provider's working directory, so on an image whose working directory is /root the default call targeted /root/skills and failed with PermissionError. It now installs under the scope's cwd, matching how exec(), read_file() and write_file()...
feat(sentinel): a sentinel sidecar can free a sample's facts once its runs end UKGovernmentBEIS/inspect_ai
A sentinel sidecar holds each sample's input and metadata until the task's registration expires within a byte limit (64 MiB by default), so an eval whose sample facts exceed that limit failed partway with registrations_full. Inspect now lets the sidecar release a sample's facts once its runs end.
docs(design): sandbox identity at the sandbox-operation boundary, as built UKGovernmentBEIS/inspect_ai
The sandbox-identity design now documents what is on main: during a sandbox_identity() scope, exec(), read_file() and write_file() take the scope's user and cwd when the caller omits them, framework operations opt out via framework_sandbox_operation(), and install_skills() installs as the member when no user is given.