Handle Raised Exception To Continue Sync

[cmhedrickREI]

Pull Request

Related to GSA/data.gov#4624

About

An analysis of the issue:
The old and current rebuild calls out to our package_create which then calls out to a several other functions such as rollup_save_action then to our translate_spatial. Within the translate spatial we then call the json.dump which we do wrap in an try/except, however this caused the rebuild to fail in the update which then led to the rebuild raising the exception and then holding up the index. Switching out the raise from the original CKAN code we will instead log the package_ids of failing datasets while not holding up the entire rebuild.

I also added a test case in which we take a bad json file that I think helps test bad json that indirectly helps support this change while not directly connected with the rebuild, it does help test for JSON failing json which could trigger the issue with old harvester.

• Adds make command down to spin down containers.
• Adds minor lint change
• Cleans up docker compose file to get rid of version warning

PR TASKS

• The actual code changes.
• Tests written and passed.
• Any changes to docs?
• Bumped version number in setup.py (also checked on PyPi).

[neilmb]

LGTM, just quibbles.