-
Notifications
You must be signed in to change notification settings - Fork 486
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
TagAttributeException in logs, containing "#{empty DatasetPage.croissant}" despite croissant exporter not used by the installation #10848
Comments
FWIW: At QDR I've added https://github.com/QualitativeDataRepository/dataverse/blob/5f7db5fc288e677d7dab57adc2abe48fb4dea164/src/main/java/edu/harvard/iq/dataverse/DatasetPage.java#L5880-L5884 to avoid the stack trace, but I haven't discovered under what circumstances the workingversion is null. I do know that the problem also existed before croissant - with the getJsonLd lookup which calls the same method to see if the latestpublishedversion is being viewed. |
Huh, so it may be pre-existing, unrelated to #10382 where we added that check for Croissant. 🤔 Given a NullPointerException from
@okaradeniz if you can narrow down when this happens we'd appreciate it! Thanks for reporting this! |
Thanks! We saw it several times in the logs, but we don't know how to reproduce it yet. I'll let you know once we know more about it. |
What steps does it take to reproduce the issue?
The exception is discovered in the logs of the Dataverse installation, therefore it is not known how to reproduce it.
When does this issue occur?
The exception is logged in seemingly random times during the day.
Which page(s) does it occurs on?
N/A
What happens?
A TagAttributeException occurs. The exception contains
test="#{empty DatasetPage.croissant}"
even though the installation does not use a Croissant exporter:To whom does it occur (all users, curators, superusers)?
N/A
What did you expect to happen?
N/A
Which version of Dataverse are you using?
6.3
The text was updated successfully, but these errors were encountered: