You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im trying to reproduce a bug we have in multiple projects since one of the newer 2.3.* releases which sees the same entity being tried to be persisted twice with the same identifier in some relationship cases
While checking if i can reproduce in the tests, i managed to get an infite loop reproduced as follows.
Adding another test case to Zenstruck\Foundry\Tests\Integration\ORM\EdgeCasesRelationshipTest
There was 1 error:
1) Zenstruck\Foundry\Tests\Integration\ORM\EdgeCasesRelationshipTest::inverse_one_to_one_with_non_nullable_inverse_side_after_persist with data set "Zenstruck\Foundry\Tests\Fixture\Entity\EdgeCases\InversedOneToOneWithNonNullableOwning\OwningSide::$inverseSide - no cascade
" (Zenstruck\Foundry\Tests\Fixture\DoctrineCascadeRelationship\DoctrineCascadeRelationshipMetadata Object (...))
Error: Xdebug has detected a possible infinite loop, and aborted your script with a stack depth of '512' frames
note: this test might not fully reflect our entities and factories setup and there might still be another bug as mentioned at the start, ill try to continue reproduce it and make another bug report.
The text was updated successfully, but these errors were encountered:
Im trying to reproduce a bug we have in multiple projects since one of the newer 2.3.* releases which sees the same entity being tried to be persisted twice with the same identifier in some relationship cases
While checking if i can reproduce in the tests, i managed to get an infite loop reproduced as follows.
Adding another test case to
Zenstruck\Foundry\Tests\Integration\ORM\EdgeCasesRelationshipTest
leads to
note: this test might not fully reflect our entities and factories setup and there might still be another bug as mentioned at the start, ill try to continue reproduce it and make another bug report.
The text was updated successfully, but these errors were encountered: