fix: fix hasCollection response has no status

[wayblink]

issue: #37257

[mergify]

@wayblink Please associate the related issue to the body of your Pull Request. (eg. “issue: #”)

[mergify]

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

[congqixia]

/lgtm

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.88%. Comparing base (86b9c3e) to head (56b4b77).
Report is 31 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #37254      +/-   ##
==========================================
- Coverage   83.15%   80.88%   -2.27%     
==========================================
  Files        1029     1319     +290     
  Lines      157251   182666   +25415     
==========================================
+ Hits       130764   147754   +16990     
- Misses      21322    29734    +8412     
- Partials     5165     5178      +13     

Components	Coverage Δ
Client	∅ <ø> (∅)
Core	67.16% <ø> (∅)
Go	83.13% <100.00%> (-0.06%)	⬇️

Files with missing lines	Coverage Δ
internal/proxy/task.go	87.05% <100.00%> (+0.02%)	⬆️

... and 318 files with indirect coverage changes

[wayblink]

/run-cpu-e2e

[mergify]

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

[mergify]

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

[wayblink]

rerun cpp-unit-test

[mergify]

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

[congqixia]

/lgtm

[wayblink]

rerun cpp-unit-test

[mergify]

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

[mergify]

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

[czs007]

/approve
/lgtm

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: congqixia, czs007, wayblink

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

The pull request process is described here

Needs approval from an approver in each of these files:

• internal/proxy/OWNERS [congqixia,czs007]

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