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

ooni / netx / 127 / 3
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: issue/302
DEFAULT BRANCH: master
Ran 22 Oct 2019 09:14AM UTC
Files 23
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

22 Oct 2019 09:10AM UTC coverage: 100.0% (+0.1%) from 99.903%
GO111MODULE=on

Pull #38

travis-ci

web-flow
httpx: use context for propagating transaction info

The final barrier for using context for propagating transaction info
is the usage of DialTLS inside the http transport.

By switching to using DialContext instead, and by delegating to the
net/http transport the TLS handshake, we can propagate the context
everywhere, so we can always put measurements in context.

While working on that, I realised that the split between a TLS
handshake start and a TLS handshake done event was reasonable since
it allowed us to put I/O events between these two events in the
right context (i.e. TLS handshake I/O) as well.

In the same vein, I should probably split the Resolve event into
two separate events, to put resolve operations in context.
Pull Request #38: httpx: use context for propagating transaction info

991 of 991 relevant lines covered (100.0%)

27.42 hits per line

Source Files on job 127.3 (GO111MODULE=on)
  • Tree
  • List 0
  • Changed 13
  • Source Changed 12
  • Coverage Changed 12
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 212
  • Travis Job 127.3
  • 5db5ba0d on github
  • Prev Job for GO111MODULE=on on feature/refactor-10 (#123.1)
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