You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Nov 9 this repo had 5 open PRs and 6 open issues. Try each PR and check each issue against main.
Done when
Every open PR and issue has a triage comment from this pass
Summary comment here
How to triage each item:
Read it, and for a PR check out the branch and try the change: build it, run the tests it touches, and exercise the behaviour it claims (for an issue, try to reproduce it on current main).
Check CI, conflicts, unanswered review feedback, and whether it is a genuine, in-scope contribution.
Leave a comment with the outcome and a next step: ready to merge (and why), needs changes (specific), duplicate or already fixed (link it), or close (with the reason).
Link it to the epic or issue it belongs to, and label it.
Tracking issue for a one-off triage pass over the repo's open PRs and issues (5 PRs, 6 issues) against main, with per-item triage comments and a summary. This is process/coordination work, not a bug or feature; low urgency since it is a scheduled housekeeping milestone task.
Status update, 2026-11-11 14:50 IST: merged #148. The tables below are the triage as it was done; rows for those items are now settled.
tinybox: open PR triage (tinybox#151, team#45)
Official main 7146de6. openhuman pins 8febf22 = v0.2.5: 6 commits behind main, no source or contract change between them (sha2 bump only), contract (2, 3) on both. Tested on our CI runner: #150, #149 and #148, each merged onto main. Main's Windows feature-tests fails on the run_native_shell_* tests (run 42013264157), and the three dependabot PRs fail only that job.
CF green (build, clippy, 631 tests). One codex P2 is unanswered: closing one of two resources sharing an adopted box deletes the shared record. agent37 is live in openhuman, and its 4 CreateRequest literals break on the re-pin.
File a follow-up issue for the codex P2 (closing one shared retained box strands the other); plan the openhuman re-pin, module record and literals together.
Still a real gap on main, but 785 behind, 2 conflicts, written for contract 1.20 (main is 2.3), last run red on Linux and macOS; author quiet since 10-22.
Author rebases or a fresh smaller PR; maintainer decides whether to close.
Issues
By code reading; identical at main 7146de6 and the pin 8febf22 (jail/module/host crates unchanged between them).
bwrap/mod.rs:352-367 only reports Kernel when !allow_net; no pasta/slirp4netns; Linux registry MCP servers were refused (EX63 run 39292268284, per the issue)
tinybox PR per the proposal; first confirm openhuman still sets allow_net + require_process_isolation
macos.rs:236-242 renders the deny block last with no scratch carve-out; native_shell/mod.rs:109-110 adds the scratch after prepare; denials are exact paths only
carve-out first (scratch before prepare, or re-allow it last), patterns as a separate contract change; the 0.1.36 target is stale; same grant path as #84
the contract types for every phase are on main, but no backend enforces NetworkPolicy::Allowlist, nothing emits SandboxEvent::Denied, and bwrap has no limits; the host sends resources: None from all 3 builders; openhuman#7328 is closed
narrow it to the tinybox enforcement gaps; host work → new openhuman issue (draft: tinybox-issue-27-host-draft.md)
windows.rs is now compiled on Windows (lib.rs:70-71); the AppContainer backend spawns via a crate-owned child (spawn_owned_captured); CI fences the unsafe
confirm the Windows default backend uses the owned path, then close
module-ci / supply-chain is now red on main and on re-runs: RUSTSEC-2026-0459 (libsqlite3-sys 0.38.2, C SQLite CVE-2026-119375). It comes via tinystoragedrivers 2.1.2 (rev 6226b9484c) → rusqlite 0.40.2, so the fix is a tsd release on rusqlite 0.41, then a tinybox tsd pin bump.
Activity
tinysweeper commentedon Nov 9, 2026
Tracking issue for a one-off triage pass over the repo's open PRs and issues (5 PRs, 6 issues) against main, with per-item triage comments and a summary. This is process/coordination work, not a bug or feature; low urgency since it is a scheduled housekeeping milestone task.
Labelled
priority: p3.M3gA-Mind commentedon Nov 11, 2026
tinybox: open PR triage (tinybox#151, team#45)
Official main 7146de6. openhuman pins 8febf22 = v0.2.5: 6 commits behind main, no source or contract change between them (sha2 bump only), contract (2, 3) on both. Tested on our CI runner: #150, #149 and #148, each merged onto main. Main's Windows
feature-testsfails on therun_native_shell_*tests (run 42013264157), and the three dependabot PRs fail only that job.--lockedbuild and workspace tests pass (1515/0). The only red is main's Windows flake.CreateRequestliterals break on the re-pin.Issues
By code reading; identical at main 7146de6 and the pin 8febf22 (jail/module/host crates unchanged between them).
!allow_net; no pasta/slirp4netns; Linux registry MCP servers were refused (EX63 run 39292268284, per the issue)prepare; denials are exact paths onlyprepare, or re-allow it last), patterns as a separate contract change; the 0.1.36 target is stale; same grant path as #84NetworkPolicy::Allowlist, nothing emitsSandboxEvent::Denied, and bwrap has no limits; the host sendsresources: Nonefrom all 3 builders; openhuman#7328 is closedspawn_owned_captured); CI fences theunsafeUpdate 2026-11-11 14:30 IST:
module-ci / supply-chainis now red on main and on re-runs: RUSTSEC-2026-0459 (libsqlite3-sys 0.38.2, C SQLite CVE-2026-119375). It comes via tinystoragedrivers 2.1.2 (rev 6226b9484c) → rusqlite 0.40.2, so the fix is a tsd release on rusqlite 0.41, then a tinybox tsd pin bump.