microsoft / microsoft/react-native-windows
Error out any pending RPC Request Promises if Client Closed (automation-channel)
Open
Nobody has claimed this yet.
Area: Test Infrastructure
enhancement
PR Follow-up
Workstream: Test Coverage
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
close [](start = 2, length = 5)
Should we cancel / close/empty this.pendingRequests?
Originally posted by @dannyvv in https://github.com/microsoft/react-native-windows/pull/7071#discussion_r572579520
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 automation-channel client close path and the pendingRequests lifecycle. Review how RPC Request Promises are created and settled; done means pending requests are handled when the client closes rather than remaining unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100