Skip to content

Conversation

jayantxie
Copy link
Member

@jayantxie jayantxie commented May 28, 2025

What type of PR is this?

fix

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

fix: 修复未连通网络下 tls 握手无限等待问题

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

#1366

(Optional) The PR that updates user documentation:

@jayantxie jayantxie requested review from a team as code owners May 28, 2025 09:18
Copy link

codecov bot commented May 28, 2025

Codecov Report

Attention: Patch coverage is 20.00000% with 8 lines in your changes missing coverage. Please review.

Project coverage is 73.65%. Comparing base (5513927) to head (cc9396e).
Report is 2 commits behind head on develop.

Files with missing lines Patch % Lines
pkg/network/standard/connection.go 20.00% 7 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1367      +/-   ##
===========================================
- Coverage    73.68%   73.65%   -0.04%     
===========================================
  Files          145      145              
  Lines        16860    16870      +10     
===========================================
+ Hits         12423    12425       +2     
- Misses        3848     3855       +7     
- Partials       589      590       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jayantxie jayantxie force-pushed the fix/tls_indefinite_blocking branch from e3f8ae7 to cc9396e Compare May 28, 2025 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants