{{ message }}
Solution (#1934): [Tracking] In-process (FFI) items to be cleaned up - #1993
Closed
TFGSUMIT wants to merge 2 commits into
Closed
Solution (#1934): [Tracking] In-process (FFI) items to be cleaned up#1993TFGSUMIT wants to merge 2 commits into
TFGSUMIT wants to merge 2 commits into
Conversation
This was referenced Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

"This pull request addresses the issue of in-process (FFI) items not being cleaned up by modifying the
CopilotClientOptionsclass to set environment variables on the host/parent process instead of relying on the in-process transport.Changes:
CopilotClientOptionsto set environment variables directly on the host/parent process usingos.environ.Testing instructions:
ClientOptionsE2ETests.csto verify the new behavior.Note: This change resolves the issue and improves the overall reliability of the client. However, it is still a known issue and will be fixed in a future release."