I noticed this comment on IRC:
<puiterwijk> tflink: there's issues with the fedmsg-meta for taskotron: WARNING:fedmsg.meta:Unhandled taskotron type u'compose'
I'm not exactly sure what the problem is, I didn't know we even use that item type. But we should look into it. Also check which other new types (we've added many new recently) are not handled well by fedmsg-meta, and figure out whether there's some better approach than manually adding each type to fedmsg-meta.
I'm not exactly sure what the problem is, I didn't know we even use that item type.
For the record, we use that type for atomic and cloud checks.
'compose' is in the canonical list of accepted types: https://pagure.io/taskotron/libtaskotron/blob/develop/f/libtaskotron/check.py#_244
! In #948#13684, @roshi wrote: 'compose' is in the canonical list of accepted types: https://pagure.io/taskotron/libtaskotron/blob/develop/f/libtaskotron/check.py#_244
I'm not sure that's relevant here - I'm pretty sure that the error is coming out of fedmsg-hub which is long before any data gets to libtaskotron.
Metadata Update from @kparal: - Issue tagged with: infrastructure
Log in to comment on this ticket.