Skip to content
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

Specify "argument should not be null" exception #996

Closed
Kira-Cesonia opened this issue Jul 3, 2020 · 2 comments
Closed

Specify "argument should not be null" exception #996

Kira-Cesonia opened this issue Jul 3, 2020 · 2 comments
Labels

Comments

@Kira-Cesonia
Copy link

Kira-Cesonia commented Jul 3, 2020

Frontend has handed me the following error stemming from our new Javers implementation:

Exception in thread "Thread-143" java.lang.IllegalArgumentException: argument should not be null
	at org.javers.common.validation.Validate.argumentsAreNotNull(Validate.java:33)
	at org.javers.core.JaversCore.commit(JaversCore.java:80)
	at org.javers.core.JaversCore.commit(JaversCore.java:69)

The problem is that this error does not happen in the backend tests that I have, and just from the error message, I can't say which of the possible arguments is null.

It would be great if the error message could specify which of the arguments was null.

@bartoszwalacik
Copy link
Member

bartoszwalacik commented Jul 3, 2020

agreed, contribute a PR, we will merge it

@bartoszwalacik
Copy link
Member

bartoszwalacik commented Jul 4, 2020

fixed in 5.10.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants