nanocoap_vfs: add nanocoap_vfs_put()#17962
Conversation
4129bbd to
2999b4c
Compare
5a63379 to
8c38feb
Compare
fabian18
left a comment
There was a problem hiding this comment.
Two nitpicks inline. PUTting and re-GETting a file works well, also with BWT.
8c38feb to
d30052a
Compare
fabian18
left a comment
There was a problem hiding this comment.
Something I have not noticed before. The first transfer goes well, but during the second or sometimes the third, the client seems to send the blocks twice and sys/net/application_layer/nanocoap/sock.c:187 fires.
nanocoap_vfs-put.pcapng.txt
7ebbe7d to
639dce8
Compare
|
Uh good catch! |
|
No |
Thanks for the hint. |
|
Hm maybe we have a bug in gnrc_sock. I see something similar with SUIT update when routing it via an intermediate RIOT node, but that might also be something else - still investigating. |
|
When I tried to reproduce this on |
|
Stack size is not the problem. I also had to increased stack sizes with: But this is just may configuration, and is probably not necessary for everyone. |
b2c9052 to
6447828
Compare
|
I'm still looking for a way to reproduce this - do you also see this issue with the |
|
Yes it also happens with |
|
So what are we going to do? The error does not come from this PR. This PR looks fine. It is something with |
|
Thank you! |
Contribution description
This adds a function to upload a file from VFS to a CoAP server via block-wise PUT request.
Testing procedure
You can test this with
aiocoap-fileserver -w:download a file from the CoAP server
upload the file again under a different name
the files should be identical
Issues/PRs references
depends on
#17937,#17960,#17958