-
-
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
index out of bounds related to searching #10373
Comments
Do you have the entry editor open when switching? if yes, any specific tab? |
I don't think I have an entry editor open for this error to occur. |
though with the editor, bibtex code, opened, I seem to regularly get ... Log File
|
The second one seems to be related to searching, for the first one I maybe have an idea for a fix. This refers to search: |
Can you test around with this version? https://builds.jabref.org/pull/10389/merge |
I assume, it did not happen with version 5.9 - or did it? |
No need to check, v5.9 doesn't work either. Update: I checked down to v5.6 - none of them worked here. |
so, does the newest development version work or not? |
I think, this is a duplicate of #8719. |
I also got an exception when searching. The same exception came up twice. Searched for a term that came up with 1 result. No entry editor open, but I have the groups tab open. This happened a couple of times before on the same version, but now if I try to reproduce it, I don't get the exception anymore, no matter the search term or if I get results. But I hope the info helps. JabRef 5.10--2023-09-01--779e555 |
JabRef version
Latest development branch build (please note build date below)
Operating system
GNU / Linux
Details on version and operating system
JabRef 5.11--2023-09-06--afb1a25 Linux 6.4.14-200.fc38.x86_64 amd64 Java 21-internal JavaFX 20+19
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
it appears when switching between two libraries, but not always.
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: