Custom entry types might crash JabRef on start

[Doc73]

JabRef version

5.13 (latest release)

Operating system

GNU / Linux

Details on version and operating system

Debian Unstable Gnome AMD64

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. $ /opt/jabref/bin/JabRef
2. Here is the result:

Messages are not initialized before accessing key: Display help on command line options
2024-04-01 23:52:12 [main] org.jabref.Launcher.main()
ERROR: Unexpected exception: java.lang.IllegalArgumentException: Fields [PAGES] already added
	at org.jabref@5.13.60000/org.jabref.model.entry.BibEntryTypeBuilder.withImportantFields(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.logic.importer.util.MetaDataParser.parseCustomEntryType(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.lambda$getBibEntryTypes$5(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.getBibEntryTypes(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.lambda$getCustomEntryTypesRepository$3(Unknown Source)
	at java.base/java.lang.Iterable.forEach(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.getCustomEntryTypesRepository(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.Launcher.initGlobals(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.Launcher.main(Unknown Source)

Appendix

...

Log File

Messages are not initialized before accessing key: Display help on command line options
2024-04-01 23:52:12 [main] org.jabref.Launcher.main()
ERROR: Unexpected exception: java.lang.IllegalArgumentException: Fields [PAGES] already added
	at org.jabref@5.13.60000/org.jabref.model.entry.BibEntryTypeBuilder.withImportantFields(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.logic.importer.util.MetaDataParser.parseCustomEntryType(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.lambda$getBibEntryTypes$5(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline$2$1.accept(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.getBibEntryTypes(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.lambda$getCustomEntryTypesRepository$3(Unknown Source)
	at java.base/java.lang.Iterable.forEach(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.preferences.JabRefPreferences.getCustomEntryTypesRepository(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.Launcher.initGlobals(Unknown Source)
	at org.jabref@5.13.60000/org.jabref.Launcher.main(Unknown Source)```

</details>

[Doc73]

P. S.: downgraded to v. 5.12, still working

[Siedlerchr]

Thanks for the report, seems like an issue with custom entry types. Do you have a custom entry type with the field Pages? Maybe the field is added twice? Domenico Cufalo ***@***.***> schrieb am Di., 2. Apr. 2024, 00:11:

…

P. S.: downgraded to v. 5.12, still working — Reply to this email directly, view it on GitHub <#11127 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACOFZHWEX2HPFMRNRT7IKLY3HLPXAVCNFSM6AAAAABFSIMM4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQGY2TQOBRGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[koppor]

@Doc73 Please open the file in a text editor, scroll to the very and and paste the selctor_keywords entries here.

@Comment{jabref-meta: selector_keywords:example;example-2;}

[Siedlerchr]

@koppor This has nothing to do with content selectors, it's about custom entry entry types, but yes they might exist there as well but the stack trace looks like it's coming from the value in the prefs

[Doc73]

@koppor I have not this line, but I use custom entry type. I'm not at home. Tomorrow evening I will send other infos

[Siedlerchr]

I can reproduce it now easily:

@Comment{jabref-entrytype: asdfasdf: req[pages] opt[pages]}

jabref/src/main/java/org/jabref/model/entry/BibEntryTypeBuilder.java

Lines 39 to 41 in 5cb70df

	if (!containedFields.isEmpty()) {
	throw new IllegalArgumentException("Fields " + containedFields + " already added");
	}

Hah and it is the exact line I called out in the review #11013 (review)

[Siedlerchr]

@Doc73 This version should work again https://builds.jabref.org/pull/11132/merge
The culprit is that you somehwere have a custom entry type with duplicated fields e.g. the field pages is both in required and optional fields

[Doc73]

@Siedlerchr I'll do the tests tomorrow, but I am nearly sure that I have no duplicate fields in my custom types, because I have given a look at the file itself (unfortunately, I can't past the text with my phone)