Skip to content

feat: Add Python 3 sandboxed execution endpoint (auto-committed) - #2

Open
sumansahoo1 wants to merge 2 commits into
mainfrom
keelen/iter-1-1783057699
Open

feat: Add Python 3 sandboxed execution endpoint (auto-committed)#2
sumansahoo1 wants to merge 2 commits into
mainfrom
keelen/iter-1-1783057699

Conversation

@sumansahoo1

Copy link
Copy Markdown
Owner

Summary

Built the Python 3 sandboxed execution endpoint via Write — server/src/services/sandboxRunner.js (shared security envelope: no network, 0.5 CPU, 512MB, read-only, dropped caps — inherited not re-declared), server/src/controllers/runPythonController.js (writes Solution.py + per-input input.txt, runs timeout --signal=KILL 10s python3 Solution.py via the runner, language='python', DI seam for testing), server/src/docker/python/Dockerfile (python:3-slim, non-root runner, WORKDIR /app), `

Known issues

Broken doom-loop PreToolUse hook (permission-denied opening /app/scripts/lib/doom_loop_hook.py) blocked EVERY Bash+Edit call this iter — could NOT git commit (attempted, blocked), run the red-first node --test proof, or yarn lint; changes sit uncommitted in the working tree for the wrapper. AC5 e2e is the honest Docker-required manual QA step, pending a Docker daemon. (Kaizen candidate: fix the hook script's read permissions so dev iters can commit and run red-first proofs.)

@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 6:53am

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