I finally got around to looking into this and found that a workaround
is to explicitly set (despite there being a default value according to
the docs) the compressed_image_transport_format parameter for the
nodes that use compressed_image_transport. No more logfile spew.

I'm curious if anyone else using compressed_image_transport was seeing
this, or if it is an indication that I'm doing something wrong in my
usage of that package/plugin.

Cheers,
Pat

On Fri, Apr 16, 2010 at 2:40 PM, Patrick Bouffard
<bouffard@eecs.berkeley.edu> wrote:
> I just noticed that I have a node that is emitting a bunch of messages
> into its logfile:
>
> ...
> [roscpp_internal] [2010-04-16 14:33:28,734] [thread 0xb776c980]:
> [DEBUG] XML-RPC call [searchParam] returned an error (-1): [Cannot
> find parameter [compressed_image_transport_format] in an upwards
> search]
> [roscpp_internal] [2010-04-16 14:33:29,228] [thread 0xb776c980]:
> [DEBUG] XML-RPC call [searchParam] returned an error (-1): [Cannot
> find parameter [compressed_image_transport_format] in an upwards
> search]
> [roscpp_internal] [2010-04-16 14:33:29,723] [thread 0xb776c980]:
> [DEBUG] XML-RPC call [searchParam] returned an error (-1): [Cannot
> find parameter [compressed_image_transport_format] in an upwards
> search]
> [roscpp_internal] [2010-04-16 14:33:30,219] [thread 0xb776c980]:
> [DEBUG] XML-RPC call [searchParam] returned an error (-1): [Cannot
> find parameter [compressed_image_transport_format] in an upwards
> search]
> ...
>
> I don't think I am doing anything with the
> compressed_image_transport_format; the default jpeg is fine and that
> seems to be what the node is producing.
>
> Pat
>