Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: removes the warning and fallback to the authority. #72

Merged
merged 1 commit into from
Jun 11, 2023

Conversation

jcchavezs
Copy link
Member

When the parseServerName used to fail because port wasn't present we produced a log warning which wasn't accurante nor actionable. In this commit it is being removed and relaxes the parsing to a best effort.

Closes #70

Ping @ericswpark

When the parseServerName used to fail because port wasn't present we produced a log warning which wasn't accurante nor actionable. In this commit it is being removed and relaxes the parsing to a best effort.
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot E 2 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@jcchavezs jcchavezs requested a review from M4tteoP June 11, 2023 17:02
Copy link
Member

@M4tteoP M4tteoP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, looks good to me

@jcchavezs jcchavezs merged commit 22910cb into main Jun 11, 2023
@jcchavezs jcchavezs deleted the fixes_warning_on_server_name_failure branch June 11, 2023 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Spurious "failed to parse server name" messages
2 participants