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

JabRef 3.0: ACM Fetcher: Cannot parse number of hits #545

Closed
Siedlerchr opened this issue Dec 20, 2015 · 2 comments
Closed

JabRef 3.0: ACM Fetcher: Cannot parse number of hits #545

Siedlerchr opened this issue Dec 20, 2015 · 2 comments
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@Siedlerchr
Copy link
Member

When I do a search in the ACM in JabRef (no matter which one ), I get the following error.

java.io.IOException: Cannot parse number of hits
    at net.sf.jabref.importer.fetcher.ACMPortalFetcher.getNumberOfHits(ACMPortalFetcher.java:427)
    at net.sf.jabref.importer.fetcher.ACMPortalFetcher.processQueryGetPreview(ACMPortalFetcher.java:136)
    at net.sf.jabref.importer.fetcher.GeneralFetcher$3.run(GeneralFetcher.java:241)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
@oscargus
Copy link
Contributor

I can confirm this. I've started to see if I can solve it, and have passed the hits parsing. However, many other things have changed in the search results so it may take a while to get it back.

@oscargus oscargus added the bug Confirmed bugs or reports that are very likely to be bugs label Dec 27, 2015
@oscargus oscargus self-assigned this Dec 27, 2015
oscargus added a commit that referenced this issue Dec 27, 2015
oscargus added a commit that referenced this issue Dec 27, 2015
@oscargus
Copy link
Contributor

OK, seems like I got some time on my hands anyway...

Try it out at http://builds.jabref.org/acmfetcher/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

2 participants