there is logic that references through some invalid pointer arithmetic when dealing with the
root of a directory being published, application can put unvalid/undefined characters in the
topic header of the message, and post it.
Here is a snapshot seen on the broker of the message. Note the topic with the ?? after the standardish v03.post topic:
when received by the python implementation, the result is:
2024-07-17 15:32:50,627 [WARNING] sarracenia.moth.amqp getNewMessage failed q_tfeed.subscribe.cdnld_f21.peter_SSC-5CD2310S60_43670017: 'utf-8' codec can't decode byte 0xad in position 9: invalid start byte
2024-07-17 15:32:50,627 [WARNING] sarracenia.moth.amqp getNewMessage lost connection to broker
This is causing some flow tests to fail because they all publish a tree starting from the root, shows up since directories are a thing, and since relPath is always relative.
there is logic that references through some invalid pointer arithmetic when dealing with the root of a directory being published, application can put unvalid/undefined characters in the topic header of the message, and post it.
Here is a snapshot seen on the broker of the message. Note the topic with the ?? after the standardish v03.post topic:
when received by the python implementation, the result is: