74
93%
master: 95%

Ran 07 Nov 2018 09:48PM UTC

Jobs 2

Files 3

Run time 3s

Badge

Embed ▾

pending completion

Build # 74

Build Type

push

travis-ci

Committed by

mehaase

Commit Message

Delay connection closed (#69)

As described in the issue, get_message() was raising connection closed
even if there were pending messages. Per Nathaniel's suggestion, the
proper behavior is this:

1. If the remote endpoint closed the connection, then the local endpoint
   may continue reading all messages sent prior to closing.
2. If the local endpoint closed the connection, then the local endpoint
   may not read any more messages.

I added tests for these two conditions and implemented the behavior by
closing the ReceiveChannel inside the connection's `aclose()`. This
requires a bit of additional exception handling inside `get_message()`
and inside the reader task.

One slight surprise is that the test can't be written due to the bug
in #74! The client would hang because the reader task is blocked by
the unconsumed messages. So I changed the channel size to 32, which
allows this test to work, and I will replace this hard-coded value
when I fix #74.

Run Details

343 of 373 relevant lines covered (91.96%)

1.84 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	74.1	07 Nov 2018 09:48PM UTC	0	91.69	Travis Job 74.1
2	74.2	07 Nov 2018 09:48PM UTC	0	91.96	Travis Job 74.2

Source Files on build 74

Detailed source file information is not available for this build.

HyperionGray / trio-websocket / 74
93%
master: 95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 74

HyperionGray / trio-websocket / 74 93% master: 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 74

HyperionGray / trio-websocket / 74
93%
master: 95%

README BADGES
x