fix: pass tenant to load in cascade destroy #4583
Triggered via pull request
February 7, 2025 13:11
barnabasJ
Status
Cancelled
Total duration
5m 51s
Artifacts
–
Annotations
21 errors and 2 warnings
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L304
test load allows loading paginated has_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L402
test load allows loading many_to_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L501
test load allows loading paginated many_to_many relationship on the action options (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L285
test load allows loading has_many relationship on the action options (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L355
test load allows loading paginated has_many relationship on the action options (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L425
test load allows loading many_to_many relationship on the action options (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L446
test load allows loading paginated many_to_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/destroy_test.exs#L264
test load allows loading has_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (SimpleSat) / mix test:
test/resource/changes/relate_actor_test.exs#L159
test relate_actor change works with streaming bulk create (Ash.Test.Resource.Changes.RelateActorTest)
|
|
ash-ci (SimpleSat) / mix test:
test/actions/update_test.exs#L1170
test updating with has_one relationships it sets the relationship on the destination record accordingly (Ash.Test.Actions.UpdateTest)
|
|
ash-ci (Picosat) / mix test:
test/changeset/changeset_test.exs#L1030
test manage_relationship/3 type: :append_and_remove it accepts mix of entities and maps representing primary_keys as a second param (Ash.Test.Changeset.ChangesetTest)
|
|
ash-ci (Picosat) / mix test:
test/changeset/changeset_test.exs#L935
test manage_relationship/3 type: :append_and_remove it replaces entities to a resource's relationship (Ash.Test.Changeset.ChangesetTest)
|
|
ash-ci (Picosat) / mix test:
test/filter/filter_test.exs#L583
test relationship filters filtering on a belongs_to relationship (Ash.Test.Filter.FilterTest)
|
|
ash-ci (Picosat) / mix test:
test/filter/filter_test.exs#L597
test relationship filters filtering on a many_to_many relationship (Ash.Test.Filter.FilterTest)
|
|
ash-ci (Picosat) / mix test:
test/filter/filter_test.exs#L604
test relationship filters relationship filters are honored when filtering on relationships (Ash.Test.Filter.FilterTest)
|
|
ash-ci (Picosat) / mix test:
test/filter/filter_test.exs#L576
test relationship filters filtering on a has_one relationship (Ash.Test.Filter.FilterTest)
|
|
ash-ci (Picosat) / mix test:
test/filter/filter_test.exs#L590
test relationship filters filtering on a has_many relationship (Ash.Test.Filter.FilterTest)
|
|
ash-ci (Picosat) / mix test:
test/actions/destroy_test.exs#L264
test load allows loading has_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (Picosat) / mix test:
test/actions/destroy_test.exs#L402
test load allows loading many_to_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (Picosat) / mix test:
test/actions/destroy_test.exs#L446
test load allows loading paginated many_to_many relationship on the changeset (Ash.Test.Actions.DestroyTest)
|
|
ash-ci (Picosat) / mix dialyzer
FailFast: cancelling since parallel instance has failed
|
|
ash-ci (SimpleSat) / mix sobelow
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
|
|
ash-ci (Picosat) / mix sobelow
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
|