codedge-llc / kadabra

88%

master: 87%

LAST BUILD ON BRANCH v0.4.2

branch: v0.4.2

CHANGE BRANCH

x

Reset

• v0.4.2
• better-queue
• chore/mix-cleanup
• ci/elixir-10-travis
• feat/keep-bin
• feat/less-process
• feat/params
• feat/socket
• fix/already-started
• fix/better-window-update
• fix/certifi
• fix/connection-sup
• fix/dual-settings
• fix/no-proc
• fix/proper-close
• fix/remove-warnings
• fix/temporary-restart
• flow
• master
• max-frame-size-fix
• new-sup
• refac/hpack
• socket-gen
• v0.3.5
• v0.3.6
• v0.3.7
• v0.3.8
• v0.4.0
• v0.4.1
• v0.4.3
• v0.4.4
• v0.4.5
• v0.5.0
• v0.6.0

Build # 308

Build Type

push

travis-ci

Committed by web-flow

Commit Message

fix: proper supervision cleanup (#35)

* fix: proper supervision cleanup WIP

* fix: everything now supervised under :kadabra app

Was the original setup a while back. Supervisor was quitting
with :shutdown during cleanup, which would shutdown the process
that originally start_link'd it.

* fix: timeout on stream WindowUpdate

Replies immediately so connection can continue on with its life.
Call timeout was previously crashing connection on occasion.

* refactor: minor refactoring

* feat: CONTINUATION for sending large headers WIP

Chunks correctly, but remotes are still terminating with a
COMPRESSION_ERROR.

Possible ideas why:
1. Hpack is encoding the fragment wrong
2. Frames are being sent out of order
3. Continuation frames are being serialized wrong
4. Remotes aren't equipped to handle such large headers
5. Sending a 20mb header is just a shitty thing to do

* fix: don't crash Connection if Socket closed

Fixed by not shutting down Kadabra.Socket if the socket closes. Bins
sent to a closed socket are simply ignored.

Sending CONTINUATION frames is mostly there. Fairly certain the issue is
with hpack, so I'll need to figure something out.

* chore: bump version and update changelog

* test: increase test coverage

Run Details

432 of 491 relevant lines covered (87.98%)

12860.95 hits per line