Bug #2069
Decoding errors of Spread and socket transport are not reported properly
| Status: | Resolved | Start date: | 10/30/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 100% | |
| Category: | Common Lisp | |||
| Target version: | rsb-0.11 |
Description
Printing rsb.transport:encoding-error instances signals an error when the value of the encoded slot is not a sequence.
Associated revisions
Fixed decoding error reporting in src/transport/conditions.lisp
fixes #2069
- src/transport/conditions.lisp (decoding-error-print-data): new
function; helper function for printing octet-vector objects and other
objects that could not be decoded successfully
(decoding-error): use `decoding-error-print-data' in report - src/transport/socket/in-connector.lisp
(notification->event in-connector notification wire-schema): just
store the notification object in the `decoding-error' condition; the
condition no longer fails to print itself in this case - src/transport/spread/in-connector.lisp
(notification->event in-connector cons t): if the octet-vector ->
fragmented-notification conversion fails, store the octet vector in
the signaled `decoding-error' condition
History
#1 Updated by J. Moringen over 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset rsb-cl|c214a0a2bba2873be4f8486429148aec65cc3995.