fix: Report integer count in 'Experiencing problems' status log

[vdusek]

Summary

The walrus operator at _basic_crawler.py:1656 binds less tightly than >, so failed_requests := X - Y > 0 was parsed as failed_requests := ((X - Y) > 0) per PEP 572. As a result, failed_requests was assigned a bool instead of the integer difference, and the periodic status log emitted:

Experiencing problems, True failed requests since last status update.

instead of the actual count.

Fix

Move the parentheses so := captures the integer subtraction and > 0 sits outside.

Regression test

Added test_status_message_reports_failed_request_count, which directly invokes _crawler_state_task with a mocked _statistics.state and a separate _previous_crawler_state, asserting the rendered message contains the integer count 3, not True.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.40%. Comparing base (3c594fe) to head (fdcdd63).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1860      +/-   ##
==========================================
- Coverage   92.41%   92.40%   -0.01%     
==========================================
  Files         158      158              
  Lines       11009    11009              
==========================================
- Hits        10174    10173       -1     
- Misses        835      836       +1     

Flag	Coverage Δ
unit	92.40% <ø> (-0.01%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 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.

[Mantisus]

LGTM