Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RuntimeError: maximum recursion depth exceeded in cmp #17

Open
ysapolovych opened this issue Oct 9, 2018 · 0 comments
Open

RuntimeError: maximum recursion depth exceeded in cmp #17

ysapolovych opened this issue Oct 9, 2018 · 0 comments

Comments

@ysapolovych
Copy link

ysapolovych commented Oct 9, 2018

I have tried to set up a pipeline following the instructions on Andy Halterman's blog. Everything goes well until I try to run the Stanford pipeline on a collection of articles in MongoDB.

It seems at first that the process goes well, but after ~20 minutes an error occurs:

RuntimeError: maximum recursion depth exceeded in cmp
INFO:StanfordSocketWrap:Subprocess seems to be stopped, exit code 1
INFO:StanfordSocketWrap:Subprocess seems to be stopped, exit code 1

I have thought that it might simply surpass the recursion limit due to the number of articles your custom scraper gets from the DW (984 in my case). The same thing happens to a collection with 409 articles in it.

Though stanford.log shows that the operation was successful:

INFO 2018-10-04 13:18:18,371: Getting today's unparsed stories from db 'event_scrape', collection 'dw_test'
INFO 2018-10-04 13:18:18,371: Querying for all unparsed stories added within the last day
INFO 2018-10-04 13:18:18,373: Returning 984 total stories.
INFO 2018-10-04 13:18:18,375: Setting up CoreNLP.
INFO 2018-10-04 17:00:42,344: Running.

I've checked the database in mongo shell with db.dw_test.findOne() - it still contains unparsed text.

Just in case, I've also tried running the collection through the Phoenix pipeline, but it got 0 sentences coded.

UPD: (just in case) I've tried to test it on mongo a collection with only 1 article and it still is the same - after numerous retries, it still throws an error I've specified above. Here is a chunk of the terminal output if it might say something in particular.

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

No branches or pull requests

1 participant