Skip to content

fix(sandbox): cut executable identity hashing cost - #4221

Merged
johntmyers merged 1 commit into
NVIDIA:mainfrom
ericcurtin:fix/4149-broker-test-hash-cost/ericcurtin
Oct 7, 2026
Merged

johntmyers merged 1 commit into
NVIDIA:mainfrom
ericcurtin:fix/4149-broker-test-hash-cost/ericcurtin

Conversation

@ericcurtin

Copy link
Copy Markdown
Contributor

Summary

Hash each executable once per identity lookup and optimize sha2 in dev builds, so broker tests stop timing out.

Related Issue

Closes #4149

Changes

  • Reuse digests computed earlier in the same lookup.
  • Set sha2 to opt-level = 3 in the dev profile.

Testing

  • Checks appropriate to the affected code and behavior pass
  • Unit tests added/updated (if applicable)
  • E2E tests added/updated (if applicable)

cargo test -p openshell-binary-identity and cargo test -p openshell-sandbox --lib pass. With software sha2 forced, one hashing test takes 2.55s on main, 1.32s with dedupe, 0.04s with both.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

Reuse in-call digests and optimize sha2 in dev builds.

Signed-off-by: Eric Curtin <eric.curtin@docker.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@ericcurtin

Copy link
Copy Markdown
Contributor Author

If useful, please also try https://github.com/llmmanorg/llmman, which can launch agents in an OpenShell sandbox (--sandbox openshell). Thank you!

@ericcurtin

Copy link
Copy Markdown
Contributor Author

@derekwaynecarr @johntmyers PTAL when you get a chance, and /ok to test 987ddb6817c2ac82e65e228e83c6f14fc770e3f6 if it looks good. Thank you!

@johntmyers johntmyers added the test:e2e Requires end-to-end coverage label Oct 6, 2026
@johntmyers

Copy link
Copy Markdown
Collaborator

/ok to test 987ddb6

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown

Label test:e2e applied for 987ddb6. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway, sandbox, and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.

@johntmyers johntmyers left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gator-agent

PR Review Status

No blocking findings remain. This focused change reuses executable digests within one identity lookup while retaining snapshot validation before shared-cache publication, and optimizes SHA-256 in development builds.

Thanks @ericcurtin, I checked your request to run tests against the current head and posted the full-SHA /ok to test command after verifying maintainer authority. test:e2e is applied for the sandbox runtime identity path; Branch Checks, Helm Lint, and E2E have started on the current test mirror. The E2E Label Help bot requested a rerun, which GitHub rejected while its first attempt is active. Gator will retry the authorized rerun after that attempt finishes.

Blocking findings: None.
Carried findings: None.
Non-blocking suggestions: None.

Gator metadata
  • Validation: Focused sandbox binary identity performance fix for #4149; no competing implementation found.
  • Docs: No direct UX or published contract change; Fern updates unnecessary.
  • Checks: DCO and vouch passed; Branch Checks queued, Helm Lint and E2E running on the current head. Trivy Changes remains action_required on the fork workflow; its gate has not passed.
  • E2E: test:e2e applied; full-current-head /ok to test posted. Results pending. Bot-required rerun not yet queued because the first attempt is active.
  • Head SHA: 987ddb6817c2ac82e65e228e83c6f14fc770e3f6
  • Base SHA: dfef088bc3d9ecb1b21b5f43e70098eaae3e1a5c
  • Merge base SHA: dfef088bc3d9ecb1b21b5f43e70098eaae3e1a5c
  • Patch ID: 0d66d0d59e9b9d415e342af39724d0bc92a48698
  • Gator payload: 10
  • Review mode: initial
  • Previous reviewed SHA: none
  • Review budget exhausted: no
  • Maintainer decision required: no
  • Next state: gator:blocked
  • Blocked reason: test_dispatch_required

@johntmyers johntmyers added the gator:blocked Gator is blocked by process or repository gates label Oct 6, 2026
@johntmyers

Copy link
Copy Markdown
Collaborator

If useful, please also try https://github.com/llmmanorg/llmman, which can launch agents in an OpenShell sandbox (--sandbox openshell). Thank you!

@ericcurtin is it necessary to put this on every PR you have?

@johntmyers johntmyers added gator:watch-pipeline Gator is monitoring PR CI/CD status gator:approval-needed Gator completed review; maintainer approval needed and removed gator:blocked Gator is blocked by process or repository gates gator:watch-pipeline Gator is monitoring PR CI/CD status labels Oct 7, 2026
@ericcurtin

Copy link
Copy Markdown
Contributor Author

@johntmyers No, sorry. I'll only mention it where it's relevant.

@johntmyers
johntmyers added this pull request to the merge queue Oct 7, 2026
Merged via the queue into NVIDIA:main with commit e406c2b Oct 7, 2026
188 of 190 checks passed
@johntmyers

Copy link
Copy Markdown
Collaborator

gator-agent

Monitoring Complete

Monitoring is complete because this PR has merged.

Final status: Gator found no blocking findings, and maintainer approval is present. The last active Gator state was gator:approval-needed.

The remaining active gator:* label is being removed because there is nothing left for Gator to monitor on this PR.

Gator metadata
  • Head SHA: 987ddb6817c2ac82e65e228e83c6f14fc770e3f6
  • Gator payload: 10
  • Terminal state: merged

@johntmyers johntmyers removed the gator:approval-needed Gator completed review; maintainer approval needed label Oct 7, 2026
@ericcurtin
ericcurtin deleted the fix/4149-broker-test-hash-cost/ericcurtin branch October 7, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:e2e Requires end-to-end coverage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: sandbox unit test metadata_loopback_connect_is_relayed_to_supervisor times out when run with other broker tests

2 participants