-
Notifications
You must be signed in to change notification settings - Fork 42
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
Cannot run Quickscrape in headless mode #63
Comments
Thanks for the report. Pull requests are very welcome with the changes you have made :) |
lanzer
pushed a commit
to lanzer/thresher
that referenced
this issue
Oct 29, 2015
…-headless or -h" is supplied on quickscrape.js ContentMine/quickscrape#63
lanzer
pushed a commit
to lanzer/quickscrape
that referenced
this issue
Oct 29, 2015
…perBox, this, along with the fix on scraperBox.js will enable headless mode for quickscrape ContentMine#63
This was referenced Oct 29, 2015
Done. Should I do the same for the "response status" bug also? |
Thank very much. If you are willing, yes a PR fixing any bug is welcome :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
running quickscrape with the -h or --headless option will not launch casper
I noticed that the headless parameter is not being passed when adding the scraper through scraperbox:
quickscrape.js (211)
Also, scraperbox need to pass the parameter to scraper, which is ready to listen to the parameter
scraperbox.js (48)
So I've made the following adjustments:
quickscrape.js (211)
scraperbox.js (48)
I think the scraper checking routine also need to have the parameter added:
quickscrape.js (139)
Now I can see casperjs running. I noticed that 404 type status also result in the quickscrape halting. Will need to look into that.
The text was updated successfully, but these errors were encountered: