Invalid snapshots state about ash_postgres HOT 5 CLOSED

Ah.. it looks like the snapshots are broken because someone else introduced a change on the same resource (without a git conflict). This mechanism is a pain because it is pretty hard to fix the state later :/

from ash_postgres.

Why do we even need the snapshots? Can't we rely on migrations only?

from ash_postgres.

I had to apply this:

diff --git a/elixir/lib/[filtered]/resources/user/referral_reward.ex b/elixir/lib/[filtered]/resources/user/referral_reward.ex
index 0b5adff8..dacb0294 100644
--- a/elixir/lib/[filtered]/resources/user/referral_reward.ex
+++ b/elixir/lib/[filtered]/resources/user/referral_reward.ex
@@ -33,7 +33,8 @@ defmodule [filtered].Resources.User.ReferralReward do

     attribute :fulfilled, :boolean, allow_nil?: false, default: false

-    timestamps()
+    create_timestamp :inserted_at
+    update_timestamp :updated_at
   end

   aggregates do

and regenerate snapshots manually to fix the state.

from ash_postgres.

Those should ultimately be the same thing, likely just regenerating fixed it.

from ash_postgres.

#75 this issue should resolve the issues around conflicts when using the migration generator in parallel with others.

from ash_postgres.