fix(utils): close the parent ends in PipeSet::closeParentEnds

[chennaji9]

What does this PR do?

PipeSet splits the six pipe descriptors between parent and child (per setupChildStdio()): the child owns the stdin READ end and the stdout/stderr WRITE ends; the parent owns the stdin WRITE end and the stdout/stderr READ ends.

closeChildEnds() closed the correct three descriptors, but closeParentEnds() was an exact copy of it — it closed the child-facing ends again and never closed the ends the parent actually owns. A parent calling it after fork() leaked its own pipe ends.

Two commits:

1. fix(utils): make closeParentEnds() close the parent-owned ends (stdin write end, stdout/stderr read ends).
2. fix(cli): the only caller, the non-tty parent branch of Cli::reuseContainer, called closeParentEnds() while actually needing to drop the parent's copies of the child-facing ends — switch it to closeChildEnds(). (It worked before only because the old closeParentEnds() body was wrong in exactly that way.) The parent then adopts the parent-owned ends via releaseWriteEnd()/releaseReadEnd() for the epoll forwarding loop, unchanged.

Validation

• New unit test PipeSet.CloseParentEndsKeepsChildEndsOpen: after closeParentEnds(), fcntl(F_GETFD) confirms the child-facing ends are still open while the parent-facing ends are closed.
• Full test suite on this branch: ctest -j4 → 737/737 passed (includes all existing Cli/utils tests — no regressions from the reuseContainer change).
• Full project build passes.

🤖 Generated with Claude Code

[deepin-ci-robot]

Hi @chennaji9. Thanks for your PR.

I'm waiting for a OpenAtom-Linyaps member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
libs/linglong/src/linglong/cli/cli.cpp	0.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
libs/utils/src/linglong/utils/io/pipe.h	40.74% <100.00%> (+2.44%)	⬆️
libs/linglong/src/linglong/cli/cli.cpp	5.07% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.