• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

go-sql-driver / mysql / 25598140030 / 10
83%
master: 83%

Build:
Build:
LAST BUILD BRANCH: fix/ParseDSN-colon-in-username
DEFAULT BRANCH: master
Ran 09 May 2026 01:22PM UTC
Files 18
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 May 2026 09:50AM UTC coverage: 82.143% (+0.02%) from 82.125%
25598140030.10

Pull #1768

github

Nghĩa Nguyễn Ngọc
dsn: use last colon before '@' as user/password separator

ParseDSN was using the first colon before '@' as the separator between
username and password. This prevented usernames containing colons from
being represented in the DSN.

The DSN format already handles multiple ambiguous delimiters by scanning
from the right (e.g. the last '/' for the database name, the last '@'
for the credentials boundary). Apply the same right-to-left strategy
for the colon: use the last ':' before '@' as the user/password split
point so that usernames like "domain:user" work correctly.

Fixes #1747
Pull Request #1768: dsn: use last colon before '@' as user/password separator (fixes #1747)

3358 of 4088 relevant lines covered (82.14%)

83173.21 hits per line

Source Files on job Linux-Go-1.25-DB-9.0 - 25598140030.10
  • Tree
  • List 18
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 25598140030
  • bff59f9f on github
  • Prev Job for on fix/ParseDSN-colon-in-username (#25111743223.7)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc