Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO_RESPONSE not supported in 1.0.1 #15

Open
jknisley opened this issue Dec 26, 2018 · 0 comments
Open

NO_RESPONSE not supported in 1.0.1 #15

jknisley opened this issue Dec 26, 2018 · 0 comments

Comments

@jknisley
Copy link

jknisley commented Dec 26, 2018

When using CoAPthon3==1.0.1, deserializing messages with the NO_RESPONSE option set throws an error:

Traceback (most recent call last):
  File "main.py", line 12, in <module>
    coap_message = Serializer.deserialize(data, addr)
  File "/tmp/coapthon/serializer.py", line 78, in deserialize
    (opt_critical, _, _) = defines.OptionRegistry.get_option_flags(current_option)
  File "/tmp/coapthon/defines.py", line 166, in get_option_flags
    opt_bytes = array.array('B', '\0\0')
TypeError: cannot use a str to initialize an array with typecode 'B'

It appears that version was published before NO_RESPONSE was added to coapthon.defines.OptionRegistry. Installing from the master branch works fine, but I was just curious if there were any plans to push a new release in the near future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant