fix(ci): repair main branch regressions - #11170
Conversation
Signed-off-by: San Dang <sdang@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR updates Hermes environment validation to accept mode ChangesHermes environment boundary
Onboarding recovery
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change restores onboarding recovery fixture behavior and permits the intended transitional Hermes directory mode without allowing the adjacent world-readable posture. No actionable merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Signed-off-by: San Dang <sdang@nvidia.com>
Signed-off-by: San Dang <sdang@nvidia.com>
Signed-off-by: San Dang <sdang@nvidia.com>
|
PR Review Advisor finished for commit |
<!-- markdownlint-disable MD041 --> ## Outcome Hermes creates its fresh Kanban schema in one SQLite transaction. This avoids one synchronous disk commit for each schema statement during managed-image startup. ## Reason Hermes 0.20.6 opens the Kanban database in autocommit mode with `synchronous=FULL`, then calls `conn.executescript(SCHEMA_SQL)`. Without an explicit transaction, SQLite commits each `CREATE` statement separately. Slow overlay storage can therefore keep the gateway outside the three-minute health gate. #11170 fixed permission validation. It did not change this Kanban initialization path, so rebuilding the image exposed the existing startup delay. ## Changes - Require the pinned Hermes source to contain one `conn.executescript(SCHEMA_SQL)` call. - Wrap that call with `BEGIN IMMEDIATE` and `COMMIT` during the image build, then compile the module. - Make the legacy root-entrypoint fixture clear inherited directory special bits with GNU `chmod`'s five-digit form. ## Verification - `npm run validate:pr` passed against canonical `main` at `efd56a372999acc9d97936e9b30b2164743255a5`. - `npm run checks:repository` and the exact E2E mock/live parity gate passed. - Focused `e2e-support` validation passed: 13 tests. - GNU coreutils 8.32 in Ubuntu reproduced `0750 -> 2750` and verified `00750 -> 750` from an inherited `03770` directory. - The diff contains no secrets, API keys, or credentials. --- Signed-off-by: San Dang <sdang@nvidia.com> --------- Signed-off-by: San Dang <sdang@nvidia.com>
Outcome
Restores the two paths failing in main CI: registry-only fresh onboarding reconstructs retained sandbox identity before gateway preflight, and Hermes legacy-layout startup accepts the trusted pre-migration directory posture.
Reason
Main CI run 34114747276 repeated both failures across attempts. The onboarding coverage added by #11124 kept its verified create checkpoint only in memory, while the Hermes hardening from #11110 rejected the safe legacy 0750 directory mode before startup could repair it.
Changes
Verification
Signed-off-by: San Dang sdang@nvidia.com
Summary by CodeRabbit