fix: handle filesystem permission errors in tab completion

[wxphaha]

Fixed filesystem error handling to prevent crashes when encountering permission denied errors during tab completion
Added std::error_code usage to avoid exceptions on filesystem operations Improved path handling with safer filesystem::path concatenation Added proper error code clearing between filesystem operations Updated Makefile with debug flag for troubleshooting

Log: Fixed filesystem permission error handling in tab completion

Influence:

1. Test tab completion in directories with restricted permissions
2. Verify no crashes occur when encountering permission denied errors
3. Test filesystem operations with various permission scenarios
4. Validate error handling in different directory access situations
5. Confirm proper behavior when changing working directories fails

fix: 修复标签页补全中的文件系统权限错误处理

修复文件系统错误处理，防止在标签页补全时遇到权限拒绝错误时崩溃
添加 std::error_code 使用以避免文件系统操作中的异常
使用更安全的 filesystem::path 连接改进路径处理
在文件系统操作之间添加适当的错误代码清除
更新 Makefile 添加调试标志用于故障排除

Log: 修复标签页补全中的文件系统权限错误处理

Influence:

1. 在受限权限目录中测试标签页补全功能
2. 验证遇到权限拒绝错误时不会发生崩溃
3. 测试各种权限场景下的文件系统操作
4. 验证不同目录访问情况下的错误处理
5. 确认更改工作目录失败时的正确行为

PMS: BUG-353821

[deepin-ci-robot]

Hi @wxphaha. Thanks for your PR. 😃

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign goldendeng for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• https:/raw.githubusercontent.com/deepin-community/template-repository/master/debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

TAG Bot

TAG: 0.0.3+num2
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

Hi @wxphaha. Thanks for your PR.

I'm waiting for a deepin-community 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.

[Zeno-sole]

/integrate

[github-actions]

AutoIntegrationPr Bot
auto integrate with pr url: deepin-community/Repository-Integration#3757
PrNumber: 3757
PrBranch: auto-integration-23424676084