{"push_id":2600249681,"size":1,"distinct_size":1,"ref":"refs/heads/wait","head":"02e07110847593d08c302cb20ead45eb9b7ba06e","before":"70c759fd81e08cabcc2aa06486c4bf53550bd427","commits":[{"sha":"02e07110847593d08c302cb20ead45eb9b7ba06e","author":{"name":"Daniel Hahler","email":"46f1a0bd5592a2f9244ca321b129902a06b53e03@thequod.de"},"message":"main: use no timeout with reader.wait and move it up\n\nIt seems like this fixes (hard to reproduce) missing messages, e.g. the\nsecond MESSAGE shows up in the journal, but gets not into\n`client.log_messages`.\n\n> 2018-05-29 01:35:00,685:INFO:i-0d2ea76e3e48e65d8:celery.worker.strategy:[none]: Received task: project.celery.send_password_reset_email_task…\n> 2018-05-29 01:35:00,774:INFO:i-0d2ea76e3e48e65d8:project.app.utils:[none]: Sending email to …\n> 2018-05-29 01:35:00,817:DEBUG:i-0d2ea76e3e48e65d8:django_ses:[none]: send_messages.throttle rate_limit='14.0'\"…\n> 2018-05-29 01:35:00,893:DEBUG:i-0d2ea76e3e48e65d8:django_ses:[none]: send_messages.sent from=…\n\nIt also seems like using `list(reader)` (to see what the real, ungrouped\nmessages look like) before the `itertools.groupby` also fixes it, or at\nleast it prevented me from triggering it.\n\nI could not reproduce it using the journal data itself and running it\nlocally, i.e. it might be related to the Python version (3.6 locally,\n3.5 in the image), or more likely to some timing issues (since they are\navailable instantly when reading them locally).\n\nMaybe there is even some special case / bug, because of the `else` being used\nwith `for` in this context.","distinct":true,"url":"https://api.github.com/repos/blueyed/journald-2-cloudwatch/commits/02e07110847593d08c302cb20ead45eb9b7ba06e"}]}
{"actor":{"display_login":"blueyed"}}