TCP Node replacing complete msg object. Not just payload

#1

Since I upgraded to 0.19 I had a new bug that I had to track down.

It seems as if the TCP Request node is now replacing the complete msg object and not just the payload.

I was able to determine this by putting a debug node prior to and immediately after the TCP request node.

I could really use a workaround until this issue gets resolved.

Thanks

Joe

0 Likes

#2

Could you post an example flow that shows this?

0 Likes

#3

A quick workaround is to use a change node before the Request node to store the values in flow variables, and a change node after it to restore the values.

0 Likes

#4

I can't provide a flow because the tcp device would not be present and the flow would not work. I did take a snapshot of the flow where you can see the debug nodes prior to and right after the TCP request. And the debug windows showing the results.

0 Likes

#5

For the workaround - what properties that are present before the TCP node do you need to pass on to the flow after the TCP node?

0 Likes

#6

LOL, it looks like it is just the srcnum. Easy. I can make that happen. Thanks for making me take a second look.

0 Likes

#7

This has already been fixed in git thanks to @boneskull and we'll release 0.19.2 tomorrow.

0 Likes

#8

Great!! Thanks!!

0 Likes