chrysn
Option decoding errors (primarily in UTF8 options, probably also in empty options, not applicable to opaque or uint) do not have tested behavior; they do raise a ValueError somewhere, but...
Currently, OSCORE is enabled on a client's request by providing OSCORE credentials to that server. A user might be misled to think that having such credentials in place is sufficient...
aiocoap-fileserver is a useful tool for SUIT deployments, and aiocoap-rd and aiocoap-proxy are possibly less mature than the file server. At the very least, the aiocoap-fileserver should be a valid...
... which led to the underlying issues of #149 and #150. Those issues are fixed but still untested.
https://github.com/chrysn/aiocoap/issues/130 has caught me by surprise, and while the immediate issue is fixed, it'll probably be good to revisit the options design -- at least the length property is really...
Appendix B of RFC7252 contains some test vectors for URI encoding, which contain some of the pathological but legal cases. After the current work on making the requested URI available...
The RD and proxy tools lack the --verbose settings of aiocoap-client. Should be provided in common CLI tools.
A use case of aiocoap in a multiprocess environment has indicated that aiocoap might run get_event_loop in the module initialization code, which it rather should not -- and no matter...
As noted in dc0dbfa2, automatic random-access Block2 requests have been severely limited because they can not cover the general case well. There are two cases where we the library could...
The proxy client (and possibly some server functionality) are broken due to the rewrite of the transports branch. As proxying is likely to become a new transport option, this issue...