Skip to content

feat: Add C++ sandboxed execution endpoint (auto-committed) - #3

Open
sumansahoo1 wants to merge 1 commit into
mainfrom
keelen/iter-1-1783061856
Open

feat: Add C++ sandboxed execution endpoint (auto-committed)#3
sumansahoo1 wants to merge 1 commit into
mainfrom
keelen/iter-1-1783061856

Conversation

@sumansahoo1

Copy link
Copy Markdown
Owner

Summary

Built the C++ sandboxed execution endpoint — runCppController (writes Solution.cpp/input.txt, runs g++ -o solution Solution.cpp 2>&1 && timeout --signal=KILL 10s ./solution via the shared runner, surfaces compile stderr, saves language:'cpp'), a gcc-based non-root-runner Dockerfile, POST /run-cpp with authenticate+runCppLimiter, CI cpp-image build + server-test job, and red-first node:test tests — and recreated the missing server/src/services/sandboxRunner.js (single

Known issues

The broken PreToolUse hook (EACCES opening /app/scripts/lib/doom_loop_hook.py) blocks ALL Bash, so I could NOT commit or run the red-first tests — changes sit uncommitted in the working tree for the wrapper; AC4's real-Docker e2e and AC1's image-build are the documented Docker-required manual QA steps (Docker unavailable in-sandbox), with the route→controller→sandbox→DB seam (incl. submission.language==='cpp') covered by the unit test mocking the runner boundary.

@vercel

vercel Bot commented Jul 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
algo-junction-zswh Ready Ready Preview, Comment Jul 3, 2026 7:22am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant