Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

review error crawler error handling #57

Open
jeffmcaffer opened this issue Mar 10, 2017 · 0 comments
Open

review error crawler error handling #57

jeffmcaffer opened this issue Mar 10, 2017 · 0 comments

Comments

@jeffmcaffer
Copy link
Contributor

From time to time there is evidence that some errors can leak out of the crawler loop. in particular, it seems possible for something marked as "being processed" to not get unmarked when it is done. This causes subsequent loops to get a request and think that it is already being processed (ie.., a collision).

Do a deep review and update tests to validate that all reject and throw cases are being handled in the loop.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant