Workaround for DOI SSL error#8158
Merged
Merged
Conversation
Member
|
Hm, but JabRef does not automatically check for newer paper versions? I doubt it will have an impact |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Quick workaround for #8126
The user reported that he can sometimes fetch data from DOI and sometimes not. Now, I think, a) JabRef checked for a new version or b) an IEEE paper was tried to be downloaded. This PR moves "fixes" for these use cases to the start of the application.
CHANGELOG.mddescribed in a way that is understandable for the average user (if applicable)