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

newrelic / nri-flex / 30795271683 / 1
31%
master: 31%

Build:
Build:
LAST BUILD BRANCH: renovate/github.com-itchyny-gojq-0.x
DEFAULT BRANCH: master
Ran 03 Aug 2026 07:56AM UTC
Files 47
Run time 1s
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

03 Aug 2026 07:52AM UTC coverage: 31.466% (-0.01%) from 31.476%
30795271683.1

Pull #667

github

sairaj18
fix: close rows in runQuery to prevent connection pool leak under db_async

runQuery never called rows.Close(), and Go's database/sql has no
finalizer to do it for you. The rows.Columns() and rows.Scan() error
paths returned early without closing, permanently leaking that
connection's slot in the pool for the life of the process (db.Close()
only reaps idle connections, not ones still marked in-use).

Under db_async with many concurrent fast queries and only 2 idle
connections kept warm by default, each leak forces more simultaneous
new connection handshakes for the remaining queries in the burst,
compounding the driver-level connection-leasing contention described
in #659.

Mirrors the deferred close pattern already used by nri-mssql's
equivalent query path.
Pull Request #667: fix: close rows in runQuery to prevent connection pool leak under db_async

2011 of 6391 relevant lines covered (31.47%)

9.06 hits per line

Source Files on job run-linux - 30795271683.1
  • Tree
  • List 47
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 30795271683
  • 98154385 on github
  • Prev Job for on fix/db-async-rows-close (#30696509708.1)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc