[IsolationSession] oneshot.md says the C# SDK has no IsolationSession create-and-run path
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open docs/development/architecture/backends/isolation-session/oneshot.md and find the "Deferred to follow-up work" section and the sentence about the C# SDK using only the state-aware lifecycle APIs. Confirm the create-and-run path in sdk/dotnet/Microsoft.Mxc.Sdk/V1/ContainerRequest.cs (Containment.IsolationSession) and MxcContainerIsolationSessionE2ETests, then remove the C# item and replace the stale spawn_sandbox reference with the current Rust SDK entry point. Done when the note matches the code and nothing in it is still deferred.
Written by the indexing model from the issue text.
Description
Brief description of your issue
docs/development/architecture/backends/isolation-session/oneshot.md lists "C# one-shot SDK support" under "Deferred to follow-up work" and says "The C# SDK still reaches IsolationSession only through the state-aware lifecycle APIs." The C# SDK has a create-and-run path: Containment.IsolationSession on ContainerRequest (sdk/dotnet/Microsoft.Mxc.Sdk/V1/ContainerRequest.cs), covered by MxcContainerIsolationSessionE2ETests. The same note names the Rust SDK's spawn_sandbox, which no longer exists. With C# support in place, nothing in the note is still deferred.
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 171
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 111
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/mxc
-
Backend-IsolationSession Issue-Bug Needs-Triage OS-Windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Backend-Seatbelt Issue-Docs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Area-Node-SDK Issue-Task
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
Area-Build Issue-Bug OS-Windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Embedded NUL in containerId can result in duplicate identitiesPossibly taken @safmswork claimed this 14 days ago. OpenBackend-ProcessContainer Issue-Bug OS-Linux OS-Windows
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/mxc#1621 · 1 comment ·
Maintainers usually reply within 2 days
Similar issues
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
zed-industries/zed#66543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ruffle-rs/rust-flash-lso#142 ·
-
area: docs type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
light-curve/light-curve-python#870 ·
Maintainers usually reply within 1 day
-
bug file-compat priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
storytold/photocraft#11330 · 1 comment ·
Maintainers usually reply within 1 day