Shane Bryldt <shane@signalwire.com>: Author Summary
Build | Completed | Code commits | Tests |
---|---|---|---|
SP › LKSW › #103 | 3 days ago | Testless build | |
SP › LT › #62 | 3 days ago |
Fix return from kws_raw_write on fragmented frame sending (#214)
* kws_raw_write should return the total number of bytes sent, not just the last fragment sent * Adjustment to make sure returns of -1 are captured as well, and fix missing spot in SSL block * Added zero to be inclusive as successful write when using raw sockets, but according to SSL lib 0 is an error so the behavior is slightly different using SSL versus not on the writing returns * Adjust the kws_write_frame so that when it sees a return <=0 it returns the error instead of the total written bytes |
Testless build |
SP › SW › #69 | 1 year ago |
Added support for blade 2.4.1 network data filtering
Updated advertised blade protocol revision
Added test for execute passing id
Merge pull request #77 from signalwire/retry-support
Retry support Merge branch 'v2.0' into blade-2.4.1-update
Fixed ttl heap overflow when sifting past the last branch into leafs (#56)
Fixed ttl heap overflow when sifting past the last branch into leafs Added cleanup callback for swclt_frame_t which will cleanup the allocated and copied data pointer that wasn't being released on every frame that was read
Remove temporary testing code
Temporary adjustment to allow for timeout testing
Removed noisey log, redid patch against v2.0 branchy
Add an additional method for blocking execute with passing id for testing
Updated to support agent and identity optional strings in connect pro? (#49)
* Updated to support agent and identity optional strings in connect process, passed through swclt_config Updated blade wire version, and added initial pass for blade.ping message, should respond to ping but does not produce it's own yet Reacts to blade.disconnect, but still does not gracefully hold messages after receiving it * Fix whitespace * Fix headers when compiling with -Wall -Wextra -Werror. Fix assertion failure caused by blade.ping. Retry support to be able to send explicit message id
Fix test
|
Testless build |
Build | Completed | Code commits | Tests |
---|
Build | Completed | Code commits | Tests |
---|
* kws_raw_write should return the total number of bytes sent, not just the last fragment sent
* Adjustment to make sure returns of -1 are captured as well, and fix missing spot in SSL block
* Added zero to be inclusive as successful write when using raw sockets, but according to SSL lib 0 is an error so the behavior is slightly different using SSL versus not on the writing returns
* Adjust the kws_write_frame so that when it sees a return <=0 it returns the error instead of the total written bytes