microsoft / microsoft/dcp

Pseudoterminal connection handler should be a separate process

Open
#175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
189
Forks
24
Avg merge
2d 16h
Merged PRs (30d)
18

Description

(probably implemented as a DCP command)

This is a follow up to https://github.com/microsoft/dcp/pull/173#issuecomment-4580775417 It will enable using terminals with persistent Executables and Containers.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the follow-up context in PR #173 and locating the pseudoterminal connection handler and DCP command entry points. Determine the process boundary needed to support terminals with persistent Executables and Containers, then validate the affected command and terminal behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.