Define the fedmsg consumer API message type #465
Comments
jeremycline
added a commit
that referenced
this issue
Aug 9, 2017
This is a short-term fix for #462. We don't know what type of object is being passed as a message. See #465 for follow-up to this. Signed-off-by: Jeremy Cline <[email protected]>
jeremycline
pushed a commit
that referenced
this issue
Aug 9, 2017
This is a short-term fix for #462. We don't know what type of object is being passed as a message. See #465 for follow-up to this. This is a cherry-pick of #462 Signed-off-by: Jeremy Cline <[email protected]>
jeremycline
added a commit
that referenced
this issue
Aug 14, 2017
This is a short-term fix for #462. We don't know what type of object is being passed as a message. See #465 for follow-up to this. Signed-off-by: Jeremy Cline <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes the API uses
dictobjects, and sometimes it usesmoksha.hub.zeromq.zeromq.ZMQMessageobjects. See #462 for the issue this causes with respect to headers. We need to define what the API is and determine where it is safe to convert the ZMQMessage object to a dictionary (or otherwise include the headers).The text was updated successfully, but these errors were encountered: