EF Core migration stuck after adding WithEndpointProxySupport(false)

[mrmyroll2]

Wanted to share my experience. After I added .WithEndpointProxySupport(false), things seemed to work at first, but then my PostgreSQL started getting stuck—especially when I tried running EF Core migrations with TDbContext.Database.Migrate().
I even tried setting a longer timeout with TDbContext.Database.SetCommandTimeout(TimeSpan.FromSeconds(120)), but no luck. As soon as I removed the .WithEndpointProxySupport(false) option, everything went back to normal.

Not sure what’s going on, but hope this is useful. Let me know if you need more info from my side. Thanks!

I also refer to this discussions

[davidfowl]

What version of aspire are you using?

cc @danegsta

[mrmyroll2]

Aspire version 9.3.1

[danegsta]

Are you also using .WithLifetime(ContainerLifetime.Persistent)? Is there any interesting output in the logs for the postgres resource?

I’m curious if there’s any indication of the migrations trying to run.

[mrmyroll2]

Are you also using .WithLifetime(ContainerLifetime.Persistent)

Yes

Is there any interesting output in the logs for the postgres resource?

From the PostgreSQL logs, it looks like the database is getting blocked on the default migration table, __EFMigrationsHistory.

I’m curious if there’s any indication of the migrations trying to run.

The migration does attempt to run as soon as the program starts.

I also tested the same source code on my colleague’s machine and encountered the same issue. I’m planning to try reproducing this with a simpler application to see if the problem persists.

[mrmyroll2]

Not sure what happened—when I tried to reproduce it using the same source code (but different migration), everything worked fine this time. 😅
The strange part is that the same issue also occurred on my colleague’s machine earlier.
I’ll need to dig deeper into the root cause—maybe one of the migrations is triggering it.