zozo123 opened a new pull request, #71672:
URL: https://github.com/apache/airflow/pull/71672

   Add a hosted Islo microVM backend to `SandboxToolset`, so all four sandbox 
tools can run from containerized Airflow workers without a local Docker daemon 
or KVM.
   
   - map `SandboxSpec` environment and network policy at provisioning time, 
refusing unsupported per-domain allowlists rather than silently weakening them;
   - use Islo's native streaming file APIs and bound command output inside the 
microVM without retaining the complete output in worker memory or VM storage;
   - enforce command deadlines by deleting timed-out sandboxes, with a 
server-side TTL as the orphan cleanup backstop; and
   - document the optional dependency and add focused unit coverage plus a 
deterministic system test.
   
   This follows the Islo backend handoff after #68847.
   
   Testing:
   
   - the complete Airflow system test passed against a real Islo microVM, 
exercising the deterministic agent, all four tools, persistence, nonzero exits, 
and teardown;
   - 45 focused unit tests passed against both the current SDK and the declared 
minimum `islo==0.3.9`;
   - ruff, ruff format, mypy, codespell, optional-dependency behavior, provider 
schema validation, and pre-commit hooks passed;
   - three Docker-backed repository hooks were unavailable while the local 
Docker daemon was stopped; CI will run them.
   
   related: #68847
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Codex (GPT-5.6)
   
   Generated-by: Codex (GPT-5.6) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   Drafted-by: Codex (GPT-5.6) (no human review before posting)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to