update from v2.34.43 to v2.34.52 failed

[shugotek]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

On a kubernetes deployment, I update image of realtime from 2.34.43 to 2.34.52 and now have an error at startup during migration part :

init-db postgresql.default.svc.cluster.local:5432 - accepting connections
supabase-realtime 07:11:47.188 [info] Migrations already up
supabase-realtime 07:11:51.077 [info] Replica region not found, defaulting to Realtime.Repo
supabase-realtime ** (exit) exited in: PartitionSupervisor.partitions(Realtime.Tenants.Migrations.DynamicSupervisor)
supabase-realtime     ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
supabase-realtime     (elixir 1.17.3) lib/partition_supervisor.ex:345: PartitionSupervisor.name_partitions/1
supabase-realtime     (elixir 1.17.3) lib/partition_supervisor.ex:431: PartitionSupervisor.whereis_name/1
supabase-realtime     (elixir 1.17.3) lib/gen_server.ex:1300: GenServer.whereis/1
supabase-realtime     (elixir 1.17.3) lib/gen_server.ex:1119: GenServer.call/3
supabase-realtime     (realtime 2.34.52) lib/realtime/tenants/migrations.ex:162: Realtime.Tenants.Migrations.run_migrations/1
supabase-realtime     /app/lib/realtime-2.34.52/priv/repo/seeds.exs:45: (file)
supabase-realtime     /app/lib/realtime-2.34.52/priv/repo/seeds.exs:13: (file)

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Deploy a Supabase with realtime in version 2.34.43
2. Wait finish of deployment
3. Update image of realtime to 2.34.52
4. See error

Expected behavior

Update Realtime to 2.34.52

System information

• OS: Node on Amazon Linux 2023 / Official docker image of Supabase Realtime (Kubernetes 1.32)

Additional context

Can it be related to change on migration on version between 2.34.43 and 2.34.52 (#1344)?

[shugotek]

I confirm that this is related to the update to version 2.34.48.
A test in 2.34.47 works, but a test in 2.34.48 gives the same error as with 2.34.52.

[filipecabaco]

Was able to replicate.

Fix here: #1352

[nthtrung09it]

Hey, when will it be merged 👯‍♂

[edgurgel]

Hey team, this should have been fixed on 2.35.3

Please feel free to reopen if that's not the case.