pgh-public-meetings / city-scrapers-pitt

Pittsburgh City Scrapers: sourcing public meetings in Pittsburgh
https://pgh-public-meetings.github.io/events/
MIT License
19 stars 66 forks source link

Cron fail: boto3 #163

Closed bonfirefan closed 3 years ago

bonfirefan commented 3 years ago

Github Action CRON issue: https://github.com/pgh-public-meetings/city-scrapers-pitt/actions/runs/238978404

Run export PYTHONPATH=$(pwd):$PYTHONPATH
Traceback (most recent call last):
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/bin/scrapy", line 8, in <module>
    sys.exit(execute())
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/lib/python3.7/site-packages/scrapy/cmdline.py", line 143, in execute
    _run_print_help(parser, _run_command, cmd, args, opts)
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/lib/python3.7/site-packages/scrapy/cmdline.py", line 98, in _run_print_help
    func(*a, **kw)
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/lib/python3.7/site-packages/scrapy/cmdline.py", line 151, in _run_command
    cmd.run(args, opts)
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/lib/python3.7/site-packages/city_scrapers_core/commands/combinefeeds.py", line 22, in run
    self.combine_s3()
  File "/home/runner/work/city-scrapers-pitt/city-scrapers-pitt/.venv/lib/python3.7/site-packages/city_scrapers_core/commands/combinefeeds.py", line 31, in combine_s3
    import boto3
ModuleNotFoundError: No module named 'boto3'
##[error]Process completed with exit code 1.
bonfirefan commented 3 years ago

uninstall city-scraper-core and re-install city-scrapers-core[aws] pipenv uninstall city-scrapers-core pipenv install city-scrapers-core[aws]

this will re-generate the pipfile lock file to get rid of the azure extras, replace aws and install boto3

will-snavely commented 3 years ago

This appears to be addressed by https://github.com/pgh-public-meetings/city-scrapers-pitt/pull/162

ben-nathanson commented 3 years ago

I agree with the previous comment. In addition, the most recent cron job after the change was successful.