unknown trigger for MalformedURLException and possible 'file' field disappearance from some entries #8510
Closed
2 tasks done
Labels
Comments
|
I had the same problem with semantic scholar links, did you import the entries via the JabRef browser extension? |
Siedlerchr
added
the
bug
|
Hey @Siedlerchr , thanks for your response. To be perfectly frank, I can't remember if I had imported these particular entries with the extension; though I do use in some occasions the JabRef extension in Firefox, I tend to manually import and fill-in some fields when I'm sure that the citation is something more complicated than an entry of type 'article' (which was most likely the case for this lengthy report). As a matter of fact, it had been a while since I last used the extension, so when I hit the button today, I noticed that---because of my latest craze to categorize configuration files and folders according to the XDG Base Directory Standard---that JabRef launched without my usual theme (and with an empty database), and with a notification to upgrade. So, after upgrading to the latest stable version and the problem persisting, I started reporting #8509, and---when inspecting the logs---that's when I discovered these exceptions. I tried adding a news article, and a scholar article (from arXiv) to try to recreate the bug, but nothing showed up in the logs to indicate there was any trouble (and I tried cleaning up and checking the integrity of all files as well). Edit: clarifying some sentences |
|
I think I found a way to reproduce it I now also get the exception: |
|
Refs #7948 which now causes problems |
|
Solution: Check if string value starts with a colon or has at least two colons or three, then go ahead and parse normally using the existing code. |
|
Huh, in my case I got a "Server returned response code: 503 for URL: ..." exception in a small pop-up. That was new to me. The exception stacktrace was: But, when checking the logs: MalformedURLException also in the logsSo, the MalformedURLException did show up in the logs. Now it's reproducible! |
This was referenced Feb 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JabRef version
Other (please describe below)
Operating system
GNU / Linux
Details on version and operating system
jabref_5.6-1_amd64.deb on Ubuntu 21.10 x86_64 with GNOME 40.5
Checked with the latest development build
Steps to reproduce the behaviour
Version info:
Details:
I'm trying to track the error, but I may need some help. If anyone more knowledgeable with the internals of JabRef can point me in a direction to try to trigger this error in a reproducible manner.
Context:
Some observations:
https://www.ipcc.ch/report/ar4/wg1/https\://www.ipcc.ch/site/assets/uploads/2018/05/ar4_wg1_full_report-1.pdfhttps://www.ipcc.ch/report/ar4/wg1/changes-in-atmospheric-constituents-and-radiative-forcing/https\://www.ipcc.ch/site/assets/uploads/2018/02/ar4-wg1-chapter2-1.pdfAs you can see, the backslash could explain the 'no protocol' message.
See appendix for BibTex source (without the file fields), and for Log File excerpt
Appendix
BibTex Source
Log File
The text was updated successfully, but these errors were encountered: