Bug #4926
closedData.wireDecode is possibly forcing the presence of metainfo tlv block
0%
Description
Hello,
I have been trying to decode a data packet encoded by the ndn-lite library, and it seems like the wire decoding of the jndn library assumes that a metainfo tlv block has to be present, even though it is optional in the Data packet specification (https://named-data.net/doc/NDN-packet-spec/current/data.html). Because of this, I get an error when trying to decode a wire encoded data packet that does not contain a metainfo tlv block.
I feel like this is likely some mistake on my part, but I cannot find where the correct data decoding function I should use to ignore these optional tlv blocks is.
I have attached screenshots of the code and output.
Files
Updated by Anonymous over 5 years ago
- Project changed from jndn to NDN-CCL
- Assignee set to Anonymous
Hi Edward. Yes, this is a bug. I moved it to the NDN-CCL projects because it affects all Common Client Libraries. I'll fix it first in jNDN and let you know.
Updated by Anonymous over 5 years ago
- Status changed from New to Feedback
@Edward Lu I pushed the fix to GitHub. Are you able to pull the latest from GitHub and test, or do you need Maven packages?
Updated by Edward Lu over 5 years ago
Ah thank you. I think I am using the Maven packages in Android Studio (I have a dependency on net.named-data:jndn-android:0.21 in my Project Structure); would that require me to use Maven packages, or should I find a way to update it in Android studio by pulling the latest version from github?
Updated by Anonymous over 5 years ago
I pushed version 0.22, so you can test the Maven package.
Updated by Edward Lu over 5 years ago
Ah thank you; I tested it and it no longer forces the presence of the metainfo block.
Updated by Anonymous over 5 years ago
Thank you for testing. I will update the other CCL libraries.
Updated by Anonymous over 5 years ago
- Status changed from Feedback to Closed
Changes pushed to master in all libraries.