net: inconsistent dial tcp error message, some have colon, some don't #45020
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Making HTTP requests and trying to handle errors
What did you expect to see?
Consistent use of the phrase
dial tcp
in error messages.What did you see instead?
Some errors from dial tcp have a colon after the tcp, some don't:
Spotted this because I'm trying to tidy the errors up a bit to give a user a bit more information, my regexp was looking for
dial tcp:
then I found the one without the colon.I've not dug in to see how may have or don't have the colon.
Thought I'd report it as it would be nice to have consistency over whether the colon is there or not.
The text was updated successfully, but these errors were encountered: