Differential D2205

Call worker_fn for each batch, instead of waiting for max_messages.
ClosedPublic
Actions

Authored by vlorentz on Oct 30 2019, 5:08 PM.

Tags

None

Subscribers

None

Details

Reviewers

Group Reviewers

Commits

rDJNL6822305a78c3: Call worker_fn for each batch, instead of waiting for max_messages.

Summary

If max_messages is 0 (the default), messages accumulate in memory and
are never processed.

Diff Detail

Repository

rDJNL Journal infrastructure

Lint

Automatic diff as part of commit; lint not applicable.

Unit

Automatic diff as part of commit; unit tests not applicable.

Event Timeline

vlorentz created this revision.Oct 30 2019, 5:08 PM

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

Harbormaster completed remote builds in B8731: Diff 7526.Oct 30 2019, 5:10 PM

vlorentz mentioned this in T2034: Unbreak journal clients.Nov 4 2019, 12:22 PM

vlorentz mentioned this in D2218: cli: fix max-message handling in the journal-client command.Nov 5 2019, 12:25 PM

olasd accepted this revision.Nov 6 2019, 1:29 PM

This revision is now accepted and ready to land.Nov 6 2019, 1:29 PM

Closed by commit rDJNL6822305a78c3: Call worker_fn for each batch, instead of waiting for max_messages. (authored by vlorentz). · Explain WhyNov 6 2019, 1:30 PM

This revision was automatically updated to reflect the committed changes.

vlorentz added a commit: rDJNL6822305a78c3: Call worker_fn for each batch, instead of waiting for max_messages..

Revision Contents
Changeset List

Path

Size

swh/

journal/

7 lines

Diff 7665

swh/journal/client.py

Loading...