gausby / tortoise
84%
master: 88%

LAST BUILD BRANCH: fix/clean-session-option
DEFAULT BRANCH: master
Repo Added
Files 34
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

LAST BUILD ON BRANCH reconnection-retries
branch: reconnection-retries
CHANGE BRANCH
x

306

Pull #47

travis-ci

web-flow 
Update changelog and bump to v0.4.0
Pull Request #47: Reconnection retries

42 of 42 new or added lines in 3 files covered. (100.0%)

510 of 610 relevant lines covered (83.61%)

31.6 hits per line

Relevant lines Covered
610 RELEVANT LINES 510 COVERED LINES
31.6 HITS PER LINE
Source Files on reconnection-retries
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
306 reconnection-retries Update changelog and bump to v0.4.0 Pull #47 web-flow travis-ci pending completion  
305 reconnection-retries Update changelog and bump to v0.4.0 push gausby travis-ci pending completion  
304 reconnection-retries Handle server side protocol violations during connection better If we cannot decode the connection acknowledgement (connack) we will exit out with a protocol violation. The server would be to blame in this situation. Pull #47 web-flow travis-ci pending completion  
303 reconnection-retries Handle server side protocol violations during connection better If we cannot decode the connection acknowledgement (connack) we will exit out with a protocol violation. The server would be to blame in this situation. push gausby travis-ci pending completion  
301 reconnection-retries Simplified the Backoff a bit and integrated it into the connector I removed the timeout from the backoff. I think this could belong to the process running the Tortoise.Connection, which simplifies the backoff quite a bit. The backoff will now wo... push gausby travis-ci pending completion  
302 reconnection-retries Simplified the Backoff a bit and integrated it into the connector I removed the timeout from the backoff. I think this could belong to the process running the Tortoise.Connection, which simplifies the backoff quite a bit. The backoff will now wo... Pull #47 web-flow travis-ci pending completion  
300 reconnection-retries Add the backoff to the connection state And add a categorize function that will allow us to send back the nature of a failed connection, allowing us to decide if we should attempt to reconnect. Pull #47 web-flow travis-ci pending completion  
299 reconnection-retries Add the backoff to the connection state And add a categorize function that will allow us to send back the nature of a failed connection, allowing us to decide if we should attempt to reconnect. push gausby travis-ci pending completion  
297 reconnection-retries Reorganize the Tortoise.Connection module Inline the connect function into the :info-handler, and made the renew function call the `:connect`-info instead of using a cast, which I could get rid of. push gausby travis-ci pending completion  
298 reconnection-retries Reorganize the Tortoise.Connection module Inline the connect function into the :info-handler, and made the renew function call the `:connect`-info instead of using a cast, which I could get rid of. Pull #47 web-flow travis-ci pending completion  
See All Builds (559)