Skip to content

Stop protocol listeners when Terminal exits - #553

Open
Gordon Lam (yeelam-gordon) wants to merge 1 commit into
dev/yeelam/reliability/embedding-handoff-timeoutfrom
dev/yeelam/reliability/wtcli-listen-disconnect
Open

Stop protocol listeners when Terminal exits#553
Gordon Lam (yeelam-gordon) wants to merge 1 commit into
dev/yeelam/reliability/embedding-handoff-timeoutfrom
dev/yeelam/reliability/wtcli-listen-disconnect

Conversation

@yeelam-gordon

Copy link
Copy Markdown
Contributor

Summary

  • heartbeat the existing ITerminalProtocol proxy so wtcli listen exits promptly when Terminal closes without reactivating the COM server
  • propagate listener EOF and abnormal spawn/read/exit failures through WTA, own the reader task, and terminate its child on channel teardown
  • pin ItE2E WTA/wtcli binaries to the selected package with package/content-addressed Store staging
  • add packaged disconnect coverage for direct wtcli listen and wta listen (C249-C250)

This is intentionally stacked on #549. The server-side handoff lease and client-side listener cleanup are separate reviewable changes; after #549 merges, this PR can be retargeted to main.

Validation

  • WindowsTerminal and wtcli x64 Debug builds
  • WTA tests: 1,396 passed, 0 failed
  • packaged combined lifecycle suite: 19 passed, 0 failed, 5 expected winapp-dependent skips
  • release report: C246-C250 checked
  • forced WTA listener spawn failure exits 1 in 238 ms with an actionable error
  • Store staged/source WTA SHA-256 hashes match

Heartbeat the existing COM proxy so wtcli listen detects server shutdown without reactivation. Propagate listener EOF and failures through WTA, own and cancel the child process, and preserve nonzero errors for abnormal startup or exit.

Add packaged direct-wtcli and WTA disconnect coverage with deterministic subscription readiness and package-pinned binaries.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: dd185e71-68e2-4772-83fe-525e877c54f4
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown

check-spelling-bot Report

⚠️ Dictionary not found

Problems were encountered retrieving check dictionaries (cspell:cpp/src/lang-keywords.txt cspell:r/src/r.txt cspell:swift/src/swift.txt cspell:cpp/src/lang-jargon.txt cspell:fullstack/dict/fullstack.txt cspell:public-licenses/src/generated/public-licenses.txt cspell:django/dict/django.txt cspell:shell/dict/shell-all-words.txt cspell:monkeyc/src/monkeyc_keywords.txt cspell:cpp/src/stdlib-cpp.txt cspell:sql/src/tsql.txt cspell:dart/src/dart.txt cspell:lua/dict/lua.txt cspell:scala/dict/scala.txt cspell:gaming-terms/dict/gaming-terms.txt cspell:golang/dict/go.txt cspell:php/dict/php.txt cspell:software-terms/dict/webServices.txt cspell:cpp/src/compiler-msvc.txt cspell:cpp/src/stdlib-cerrno.txt cspell:svelte/dict/svelte.txt cspell:cpp/src/template-strings.txt cspell:python/src/common/extra.txt cspell:elixir/dict/elixir.txt cspell:sql/src/sql.txt cspell:rust/dict/rust.txt cspell:cpp/src/stdlib-c.txt cspell:redis/dict/redis.txt cspell:powershell/dict/powershell.txt cspell:dotnet/dict/dotnet.txt cspell:cpp/src/compiler-clang-attributes.txt cspell:node/dict/node.txt cspell:python/src/additional_words.txt cspell:software-terms/dict/softwareTerms.txt cspell:latex/dict/latex.txt cspell:python/src/python/python.txt cspell:npm/dict/npm.txt cspell:cpp/src/stdlib-cmath.txt cspell:typescript/dict/typescript.txt cspell:css/dict/css.txt cspell:java/src/java-terms.txt cspell:java/src/java.txt cspell:ada/dict/ada.txt cspell:cpp/src/people.txt cspell:html/dict/html.txt cspell:ruby/dict/ruby.txt cspell:public-licenses/src/additional-licenses.txt cspell:cpp/src/compiler-gcc.txt cspell:k8s/dict/k8s.txt cspell:docker/src/docker-words.txt cspell:python/src/python/python-lib.txt cspell:haskell/dict/haskell.txt cspell:cpp/src/ecosystem.txt cspell:clojure/src/clojure.txt).

⚠️ For more information, see check-dictionary-not-found.

🔴 Please review

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

Unrecognized words (1)

DCOM

These words are not needed and should be removed AHP aiu Backgrounder CANTCALLOUT Ccc cplusplus ctl Debian depl dotnet drv endptr EOFs evt frob frobnicate Fullwidth gitlab hdr idl IME inbox ININPUTSYNCCALL INJ intelligentterminal Ioctl KVM lbl lld lsb NODEFAULT NONINFRINGEMENT notif oss outdir Podcast pri prioritization rcv segfault SND sourced SWP Tbl testname transitioning unk unparseable unregisters Virt VMs webpage websites WINVER WSLENV xsi

To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the git@github.com:microsoft/intelligent-terminal.git repository
on the dev/yeelam/reliability/wtcli-listen-disconnect branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/cfb6f7e75bbfc89c71eaa30366d0c166f1bd9c8c/apply.pl' |
perl - 'https://github.com/microsoft/intelligent-terminal/actions/runs/31076279732/attempts/1' &&
git commit -m 'Update check-spelling metadata'
Available 📚 dictionaries could cover words (expected and unrecognized) not in the 📘 dictionary

This includes both expected items (2100) from .github/actions/spelling/expect/alphabet.txt .github/actions/spelling/expect/expect.txt .github/actions/spelling/expect/web.txt and unrecognized words (1)

Dictionary Entries Covers Uniquely
cspell:csharp/csharp.txt 32 2 2
cspell:aws/aws.txt 232 2 2
cspell:fonts/fonts.txt 536 1 1

Consider adding to the extra_dictionaries array (in the .github/actions/spelling/config.json file):

    "cspell:csharp/csharp.txt",
    "cspell:aws/aws.txt",
    "cspell:fonts/fonts.txt",

To stop checking additional dictionaries, put (in the .github/actions/spelling/config.json file):

"check_extra_dictionaries": []

Pattern suggestions ✂️ (1)

You could add these patterns to .github/actions/spelling/patterns/dab992230b7e98dab2940cf0307e5662480803b6.txt:

# Automatically suggested patterns

# hit-count: 1 file-count: 1
# container images
image: [-\w./:@]+

Alternatively, if a pattern suggestion doesn't make sense for this project, add a # to the beginning of the line in the candidates file with the pattern to stop suggesting it.

Warnings and Notices ⚠️ (2)

See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.

⚠️ Warnings and Notices Count
ℹ️ candidate-pattern 1
⚠️ check-dictionary-not-found 54

See ⚠️ Event descriptions for more information.

✏️ Contributor please read this

By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.

If the listed items are:

  • ... misspelled, then please correct them instead of using the command.
  • ... names, please add them to .github/actions/spelling/allow/names.txt.
  • ... APIs, you can add them to a file in .github/actions/spelling/allow/.
  • ... just things you're using, please add them to an appropriate file in .github/actions/spelling/expect/.
  • ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in .github/actions/spelling/patterns/.

See the README.md in each directory for more information.

🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant