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

jupyter / notebook / 2383 / 1
12%
master: %

Build:
Build:
LAST BUILD BRANCH: patch-1
DEFAULT BRANCH: master
Ran 03 Jun 2016 08:13AM UTC
Files 89
Run time 4s
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 Jun 2016 08:08AM UTC coverage: 73.903% (-0.2%) from 74.091%
GROUP=python

push

travis-ci

minrk
Backport PR #1471: Fixes for reconnecting on a flaky network

Problem: When a client loses their websocket connection and then reconnects, this triggers the creation of new, identical zmq sockets with a collision in their routing IDENTITY. This causes messages to be lost, even though the websocket connection is established.

Fix: if a duplicate connection (same session id, same kernel id) is attempted, close the stale one.

My first thought was to refuse colliding connections, but for the most likely case of a flaky network where the earlier session hasn't been closed yet, this experience is quite unpleasant,
...

4834 of 6541 relevant lines covered (73.9%)

0.74 hits per line

Source Files on job 2383.1 (GROUP=python)
  • Tree
  • List 0
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 2383
  • Travis Job 2383.1
  • e15938d1 on github
  • Prev Job for GROUP=python on 4.x (#2382.12)
  • Next Job for GROUP=python on 4.x (#2384.12)
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