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

Fails on ACS #87

Open
bjonnh opened this issue Aug 15, 2016 · 4 comments
Open

Fails on ACS #87

bjonnh opened this issue Aug 15, 2016 · 4 comments

Comments

@bjonnh
Copy link

bjonnh commented Aug 15, 2016

quickscrape --scraper acs.json --url http://pubs.acs.org/doi/abs/10.1021/acs.jnatprod.6b00118 --output acs.jnatprod.6b00118 --outformat bibjson

It is stuck here:
info: quickscrape 0.4.7 launched with...
info: - URL: http://pubs.acs.org/doi/abs/10.1021/acs.jnatprod.6b00118
info: - Scraper: acs.json
info: - Rate limit: 3 per minute
info: - Log level: info
info: urls to scrape: 1
info: processing URL: http://pubs.acs.org/doi/abs/10.1021/acs.jnatprod.6b00118
Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL casperjs/bin/bootstrap.js. Domains, protocols and ports must match.

(I used the last acs.json)

@tarrow
Copy link
Contributor

tarrow commented Aug 15, 2016

Thanks so much for this bug report. I'll investigate and get back to you
about this tomorrow.

On 15 Aug 2016 7:58 p.m., "bjonnh" [email protected] wrote:

quickscrape --scraper acs.json --url http://pubs.acs.org/doi/abs/
10.1021/acs.jnatprod.6b00118 --output acs.jnatprod.6b00118 --outformat
bibjson

It is stuck here:
info: quickscrape 0.4.7 launched with...
info: - URL: http://pubs.acs.org/doi/abs/10.1021/acs.jnatprod.6b00118
info: - Scraper: acs.json
info: - Rate limit: 3 per minute
info: - Log level: info
info: urls to scrape: 1
info: processing URL: http://pubs.acs.org/doi/abs/
10.1021/acs.jnatprod.6b00118
Unsafe JavaScript attempt to access frame with URL about:blank from frame
with URL casperjs/bin/bootstrap.js. Domains, protocols and ports must match.

(I used the last acs.json)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#87, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHA020pkttRatKCdzafSSTqRNXozpgfdks5qgLa8gaJpZM4JkqgY
.

@blahah
Copy link
Member

blahah commented Aug 15, 2016

in general casperjs/phantom are no longer relevant or supported, and we should migrate to electron via nightmarejs. @tarrow whenever you feel is a good time to start looking at this move, ping me and I can help.

@petermr
Copy link
Member

petermr commented Aug 16, 2016

Thanks Richard,

The nightmarejs web page says:

"

NightmareJS is a means to communicate between a CasperJS runtime and a Node
server to allow executing of Node functions and data modification features.

NightmareJS is a means to connect CasperJS with NodeJS. There is no need to
rewrite existing CasperJS code. Instead, it passes data over a socket.io
connection between the Casper object and the Node server, allowing you to
query specific data or execute specific functions that node offers but are
unavailable in the web browser that Casper operates through.
"
Does this mean we get it working with the current system (Casper) and then
introduce electron and then remove casper? What sort of effort will this be?

Thanks

On Tue, Aug 16, 2016 at 12:49 AM, Richard Smith-Unna <
[email protected]> wrote:

in general casperjs/phantom are no longer relevant or supported, and we
should migrate to electron via nightmarejs http://nightmarejs.org.
@tarrow https://github.com/tarrow whenever you feel is a good time to
start looking at this move, ping me and I can help.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#87 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsxS0o7qC2lpekP0tNIZ5OQbZiMnN-cks5qgPrvgaJpZM4JkqgY
.

Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069

@tarrow
Copy link
Contributor

tarrow commented Sep 23, 2016

This may well be a duplicate of #62

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

4 participants