microsoft / microsoft/terminal
MiniTerm sample should specify long-running task
Open
Nobody has claimed this yet.
Area-Performance
Issue-Samples
Product-Meta
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
In the MiniTerm sample you create tasks to effectively pump IO. Since these could be long-running tasks in a practical application based on the sample, the sample should probably specify TaskCreationOptions.LongRunning to avoid consuming a couple of threads from the ThreadPool.
Contributor 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.
Research direction
Start by locating the MiniTerm sample and its task creation code; the issue does not name a file or test. Check how the sample pumps I/O and confirm which tasks may run long. Done means the sample reflects the requested long-running-task behavior without changing its purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100