Skip to content

fix(outreach): discard stale scraper results#264

Open
Gujiassh wants to merge 1 commit into
FujiwaraChoki:mainfrom
Gujiassh:fix/outreach-stale-scraper-results
Open

fix(outreach): discard stale scraper results#264
Gujiassh wants to merge 1 commit into
FujiwaraChoki:mainfrom
Gujiassh:fix/outreach-stale-scraper-results

Conversation

@Gujiassh
Copy link
Copy Markdown

Summary

  • Delete the fixed .mp/scraper_results.csv output before each Outreach scraper run.
  • Keep the existing post-run os.path.exists(output_path) guard, so a failed or timed-out scraper run no longer falls through to stale results from an earlier run.
  • Add regression coverage that simulates a stale CSV plus a failed scraper run and verifies Outreach does not read or email from the stale file.

Fixes #256.

Validation

  • python3 -m unittest tests.test_outreach_scraper_results -v
  • python3 -m unittest tests.test_post_bridge_client tests.test_outreach_scraper_results -v
  • python3 -m py_compile src/classes/Outreach.py tests/test_outreach_scraper_results.py
  • git diff --check

Note: full python3 -m unittest discover -s tests -v is blocked in this clean worktree by missing optional/runtime dependencies (srt_equalizer, termcolor) used by existing tests/modules. The focused Outreach regression and existing PostBridge client tests above pass with local dependency fakes where needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(Outreach): stale scraper_results.csv can be reused after scraper failure or timeout

1 participant