[BUG]: DOCA TCP Sensitive Information Detection Example

[e-ago]

Version

24.06

Which installation method(s) does this occur on?

Source

Describe the bug.

DOCA Source Stage originates from PreallocatorMixin which only works with MultiMessage and ControlMessage types. Although UDP examples (run_udp_raw.py and run_udp_convert.py) work well, the run_tcp.py example reports the following error.

RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type

Forum post: https://forums.developer.nvidia.com/t/doca-sensitive-information-detection-example/294898/1

Minimum reproducible example

No response

Relevant log output

Click here to see error details

[Paste the error here, it will be hidden by default]

Full env printout

Click here to see environment details

# python3 ./examples/doca/run_tcp.py --nic_addr ca:00.0 --gpu_addr 17:00.0
...
====Building Pipeline Complete!====
E20240605 08:22:01.757285 14853 builder_definition.cpp:283] Exception during segment initializer. Segment name: linear_segment_0, Segment Rank: 0. Exception message:
RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type
...
  File "/workspace/morpheus/pipeline/stage_base.py", line 396, in build
    out_ports_nodes = self._post_build(builder=builder, out_ports_nodes=out_ports_nodes)
  File "/workspace/morpheus/pipeline/single_output_source.py", line 72, in _post_build
    ret_val = self._post_build_single(builder, out_ports_nodes[0])
  File "/workspace/morpheus/pipeline/preallocator_mixin.py", line 131, in _post_build_single
    raise RuntimeError(msg)
RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type

Other/Misc.

No response

Code of Conduct

• I agree to follow Morpheus' Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report

[dagardner-nv]

@e-ago it looks like you fixed this with PR #1728 is this issue good to close?