Go ut2

[yellow-shine]

No description provided.

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yellow-shine
To complete the pull request process, please assign czs007 after the PR has been reviewed.
You can assign the PR to them by writing /assign @czs007 in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[mergify]

@yellow-shine

Invalid PR Title Format Detected

Your PR submission does not adhere to our required standards. To ensure clarity and consistency, please meet the following criteria:

1. Title Format: The PR title must begin with one of these prefixes:

• feat: for introducing a new feature.
• fix: for bug fixes.
• enhance: for improvements to existing functionality.
• test: for add tests to existing functionality.
• doc: for modifying documentation.
• auto: for the pull request from bot.

2. Description Requirement: The PR must include a non-empty description, detailing the changes and their impact.

Required Title Structure:

[Type]: [Description of the PR]

Where Type is one of feat, fix, enhance, test or doc.

Example:

enhance: improve search performance significantly 

Please review and update your PR to comply with these guidelines.

[mergify]

@yellow-shine E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@yellow-shine cpp-unit-test check failed, comment rerun cpp-unit-test can trigger the job again.

[mergify]

@yellow-shine go-sdk check failed, comment rerun go-sdk can trigger the job again.

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.

[mergify]

@yellow-shine E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

[mergify]

@yellow-shine go-sdk check failed, comment rerun go-sdk can trigger the job again.

[mergify]

@yellow-shine cpp-unit-test check failed, comment rerun cpp-unit-test can trigger the job again.

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.90%. Comparing base (585255e) to head (fbd7b07).
Report is 29 commits behind head on master.

❗ Current head fbd7b07 differs from pull request most recent head 1dfa286

Please upload reports for the commit 1dfa286 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #37227      +/-   ##
==========================================
+ Coverage   66.80%   66.90%   +0.10%     
==========================================
  Files         290      290              
  Lines       25421    25431      +10     
==========================================
+ Hits        16982    17015      +33     
+ Misses       8439     8416      -23     

see 18 files with indirect coverage changes

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.

[mergify]

@yellow-shine go-unit-test check failed, comment rerun go-unit-test can trigger the job again.