-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fetching error #3463
Comments
From the stacktrace you've posted, it looks like a bug. It shouldn't be too hard to fix. An additional null check at the respective position in code. |
It may be something on the medline side! I am experiencing multiple versions of JabRef on multiple hosts that did work with Pubmed/Medline suddenly not working today. They were working as recently as yesterday. I went and tried a recent development snapshot to make sure. 20:00:38.641 [JabRef CachedThreadPool] ERROR net.sf.jabref.FallbackExceptionHandler - Uncaught exception Occurred in Thread[JabRef CachedThreadPool,6,main] 20:07:59.728 [JabRef CachedThreadPool] ERROR org.jabref.FallbackExceptionHandler - Uncaught exception occurred in Thread[JabRef CachedThreadPool,6,main] curt@curt-laptop-ubuntu:~/bin$ java -version Did something change in the medline output recently? Is anybody else seeing this? Curt |
Possibly something has changed in the output format from medline... "Late November 2017: PubMed's MEDLINE citations, translation tables, and the MeSH database will have been updated to reflect 2018 MeSH." |
Hmmm... @curtcorum You're probably right. I try on my home computer running Ubuntu 16.04 and I get the same error, so I guess it was not my network. |
Having the same error running jabRef 4.0 on manjaro java 1.8.0_144 721953 results found. Only 50 relevant results will be fetched by default. |
It seems that they've made a part of the data (date created for articles) optional, but our code expected this to be there. @melTr @Andyroo1966 @curtcorum I have pushed a fix and Medline fetch works for me again. Could you please try out the current dev version and let me know if it works for you: http://builds.jabref.org/master/ |
@lenhard Solved for me. Got other errors in journal but unrelated to this issue. |
Ok, thanks! Then I am closing this one. |
@lenhard Working, thanks! JabRef 4.1-dev--snapshot--2017-11-29--master--42ba568ea |
Working for me also.
JabRef-4.1-dev--snapshot--2017-12-03
linux 4.13.15-300.fc27.x86_64
java 1.8.0_151
…On Thu, Nov 30, 2017 at 6:24 AM, Curt Corum ***@***.***> wrote:
Working, thanks!
JabRef 4.1-dev--snapshot--2017-11-29--master--42ba568ea
Linux 4.10.0-40-generic amd64
Java 1.8.0_151
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3463 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AggPTThlG_-XVV2mZew1DCgGlRjkhQ7rks5s7dmGgaJpZM4Qted7>
.
|
JabRef version 4 Windows7
First time I got this error. We have trouble with our university network, so it could explained. But in this case, I guess user should receive an error message (for now, it just turns endless).
Thanks
The text was updated successfully, but these errors were encountered: