swh.journal.publisher: Process origins

This simply take the origin provided by the journal listener and forwards it to the topic of reified objects.

Depends on D693

Test Plan

tox

---

Migrated from D693 (view on Phabricator)

Build is green See https://jenkins.softwareheritage.org/job/DJNL/job/tox/14/ for more details.

Same as swh-storage!128 (closed); LGTM but I really don't see what this diff is actually doing. Just reading this, seems like a convoluted way of testing the equality of a dict with itself, but I guess I miss some bigger picture...

mentioned in merge request swh-storage!128 (closed)

Merge request was accepted

approved this merge request

but I really don't see what this diff is actually doing. Just reading this, seems like a convoluted way of testing the equality of a dict with itself, but I guess I miss some bigger picture...

More details on answer [1]

• [1] https://forge.softwareheritage.org/swh/devel/swh-storage!128

convoluted way of testing the equality of a dict with itself,

Since i did not have time to unstuck me on running a real kafka instance in test context (out of scope for this week ;) I still needed to check that the data is indeed flowing through ;)

The publisher's process_objects method is the one running at the core of the publisher. Independently of the topic subscription/publishing step (which is stuck in tests for now).

So yeah, in the end, that not much. That's better than nothing though.

Rebase

Build has FAILED

Link to build: https://jenkins.softwareheritage.org/job/DJNL/job/tox/15/ See console output for more information: https://jenkins.softwareheritage.org/job/DJNL/job/tox/15/console

Rebase

Build has FAILED

Link to build: https://jenkins.softwareheritage.org/job/DJNL/job/tox/16/ See console output for more information: https://jenkins.softwareheritage.org/job/DJNL/job/tox/16/console

closed by ab56d64f a0c2b312

Merge request was merged

closed