[Pijukatel]

• StreamedLog redirects each line once its newline arrives instead of holding the last message until the next one starts, for parity with the newer JS implementation.
• Every platform log line has its own timestamp, so the redirected records are the same as before, only without the delay.

[codecov]

Codecov Report

❌ Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.73%. Comparing base (eb8ded4) to head (70d3ae4).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/apify_client/_streamed_log.py	92.30%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1219      +/-   ##
==========================================
- Coverage   95.76%   95.73%   -0.03%     
==========================================
  Files          63       63              
  Lines        6676     6678       +2     
==========================================
  Hits         6393     6393              
- Misses        283      285       +2     

Flag	Coverage Δ
integration	90.92% <92.30%> (+0.25%)	⬆️
unit	91.04% <92.30%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[apify-factory]

Looks good, nothing blocking.

🏭 Factory review — ℹ️ not auto-approved

This change was reviewed but cannot be auto-approved: a gate failed, so the review cannot end in an approval.

check	result
Static gates	❌ 15/16 — pr-open-and-ready
Review findings	✅ none
Reviewer escalation	✅ none
Juror 1 — claude-sonnet-5-5, adversarial	⏭️ skipped — a gate failed

Why it was not auto-approved

Failed gates:

• pr-open-and-ready: PR is a draft

The comments above are the review itself; this section only explains the approval decision. Push a change and request @apify-factory again to re-run it, or ask a human to review.

_{Reviewed 70d3ae486 · workflow run}

[apify-factory]

Looks good, nothing blocking.

🏭 Factory review — ℹ️ not auto-approved

Redirecting on every newline can drop continuation lines of multi-line log messages, changing the redirected output.

check	result
Static gates	✅ 16/16
Review findings	✅ none
Reviewer escalation	✅ none
Juror 1 — claude-sonnet-5-5, adversarial	❌ reject

Why it was not auto-approved

Juror 1 — claude-sonnet-5-5:

In src/apify_client/_streamed_log.py _log_buffer_content, a line is now treated as a complete message when its newline arrives, and each batch is split by the timestamp marker. Multi-line messages (e.g. tracebacks) have continuation lines with no timestamp. If such a line arrives in a later batch than its header line, it forms a batch with no marker, and re.split(...)[1:] discards it. Previously the continuation was part of the preceding message. This contradicts the claim that the redirected records are unchanged, and it also changes the public log output. Please handle continuation lines (e.g. keep the last message pending until a marker or end), add a test for a multi-line message split across chunks, and get a human review of the behavior change.

The comments above are the review itself; this section only explains the approval decision. Push a change and request @apify-factory again to re-run it, or ask a human to review.

_{Reviewed 70d3ae486 · workflow run}