-
Notifications
You must be signed in to change notification settings - Fork 96
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
NullPointerException: Parameter specified as non-null is null #1023
Comments
@Sti2nd It'll be fixed in 1.0.23. Let you know when 1.0.23 is released. Thank you. |
@Sti2nd Please check to see if the problem has been resolved. Thank you. |
@seongahjo
|
I am using the KotlinPlugin, but not sure if we generate a Kotlin type (or what you mean). Fixture Monkey only crashes for entities in our project. Perhaps JPA is the source of the problem after all. We also use Spring Boot, if that information helps. Thank you for your replies. |
@Sti2nd plugin(InterfacePlugin().useAnonymousArbitraryIntrospector(false)) Please let me know if you still have the problem. |
Describe the bug
Sometimes tests crashes with the error message:
Parameter specified as non-null is null: method my.namespace.entity.DataEntity.<init>, parameter dataSet
. Likely because FixtureMonkey tries to put null in a non-nullable field.Your environment
Steps to reproduce
Set up a code base with JPA and run the following example code. (Perhaps JPA is not needed to reproduce, I just mention it because we use it)
At first I thought it might have to do with the circular reference. However I have tried to make
DataSourceEntity.data
non-nullable, and can still reproduce.Expected behaviour
Test should run successfully
Actual behaviour
Test fails because of NullPointerException
The text was updated successfully, but these errors were encountered: