Add integration tests for SDKs

[toksdotdev]

There's currently no CI job to run lints and very that SDKs aren't broken before being merged. Stand up a CI job to do this for all SDKs we support.

[anosvoldi883]

This makes sense. I can help set up a CI job to lint and run basic integration checks for the supported SDKs. Before starting, could you confirm:

Which SDKs should be covered initially

Preferred CI platform (GitHub Actions?)

What “integration test” means here (smoke test, example usage, or full API flow)

Once clarified, I can propose a minimal CI workflow that’s easy to extend.

[toksdotdev]

awesome! we'd appreciate any form of help. whichever SDK you feel most comfortable with. but the end goal is to have similar things for all SDKs.

yes, github action. a smoke test for all the 5 endpoints supported today: start, stop, execute a command, get metrics (execute repl would soon be deprecated).

let me know if you have any other questions. i'd be happy to answer.

[anosvoldi883]

I dug into running the Microsandbox server locally and into CI feasibility.

The server requires KVM virtualization (on Linux) and Apple Silicon on macOS, which GitHub Actions runners don’t currently provide. Because of that, starting msb server (or running sandboxes) isn’t possible on standard GitHub-hosted CI runners today.

My proposal for an initial step would be:

Add a GitHub Actions workflow that validates SDKs at the installation and API surface level (e.g., install SDKs, import core modules, basic smoke checks)

Explicitly skip runtime sandbox execution in CI, with clear documentation explaining the KVM limitation

This would give us immediate value (catching packaging/import regressions) while keeping the workflow extensible for future self-hosted runners or KVM-enabled CI.

If this approach sounds good, I can start by implementing it for the Python SDK and structure it so other SDKs can be added easily later.

[toksdotdev]

Correct that we need KVM :)

I stood up a self-hosted Linux x86_64 runner yesterday to kickstart this work. The name of the runner is self-hosted-Linux-x86. We can run all of the SDK jobs on this runner.

But the direction you proposed sounds good to me. 💯 It doesn't have to be done in one go.

[anosvoldi883]

@toksdotdev i have raised a pr to Add Python SDK CI checks on self-hosted runner , it requires workflow approval
#375