AshPaperTrail Errors with Managed Relationships (?)

[DGollings]

Issue Description

After adding the ash_paper_trail extension to our resources, operations that use managed relationships :direct_control are failing.

Error Details

When attempting operations that create/update associated resources via managed relationships, we encounter
the following error:

  %Ash.Error.Unknown{
    bread_crumbs: ["Error returned from: Order.create"],
    changeset: "#Changeset<>",
    errors: [%Ash.Error.Unknown.UnknownError{
      error: "** (ArgumentError) unknown field `:paper_trail_versions` in schema Address 
  given to insert_all. Unwritable fields, such as virtual and read only fields are not supported. 
  Associations are also not supported",
      field: nil,
      value: nil,
      splode: Ash.Error,
      bread_crumbs: ["Error returned from: Order.create"],
      vars: [],
      path: [:address, 0],
      stacktrace: #Splode.Stacktrace<>,
      class: :unknown
    }]
  }

When It Occurs

• During operations using direct_control managed relationships
• When creating resources that have nested resources managed via relationships
• Specifically with operations that might trigger bulk database operations

Steps to Reproduce

1. Add the AshPaperTrail.Resource extension to resources
2. Configure appropriate domain extensions and version table resources
3. Perform operations that use direct_control relationships to create/update nested resources

Environment Details

• ash_paper_trail version: 0.5.3
• Ash version: 3.5.5

Notes

• The error specifically mentions the :paper_trail_versions virtual field during insert_all operations
• Standard create/update operations work fine
• Only fails with operations that trigger bulk processing of managed relationships
• Other resources without :direct_control seem to work fine

[zachdaniel]

Hmm...pretty strange. Would it be possible to create a reproduction? I'm quite busy these days unfortunately.

[zachdaniel]

Yeah, I don't see any reason why we'd somehow be trying to provide a relationship as a field here. Will need an end to end repro w/ ash_postgres to address.

[DGollings]

Not unwilling to make a reproduction, just wondering how to do so effectively (there's always the chance that I remove/change something and it suddenly works)

Also whether to make a new repo or trim down our resources

Any suggestions for a repro repo I could maybe fork? See if it can be reproduced? There's this Ash demo app for example right? Songz iirc

[zachdaniel]

My suggestion is to use the installer on https://ash-hq.org and build up your reproduction from scratch as ultimately the best thing is for a reproduction to be minimal. With that said, if you have trouble minimizing the reproduction you can use something larger or work it into something like tunez.