dotnet run app.cs, on a small program with a DbContext, stopped with Model building is not supported when publishing with NativeAOT. I wasn't publishing anything. File-based apps turn native AOT on by default, and one line at the top of the file turns it off.
The same burst of 600 requests crashed my API from curl and passed from PowerShell, and I nearly wrote that it only happened on one operating system. It was my PowerShell command: asked for 300 at a time, ForEach-Object -Parallel never got past 87.
The certificate is invalid was about my client certificate, the one VerifyFull needs in SslCert. I'd made it with the usual openssl req -x509, which marks a certificate as a certificate authority on a normal setup, and the driver doesn't accept a CA in that spot.
MySqlConnection.ClearAllPools() is static, so I wrote await MySqlConnection.ClearAllPoolsAsync(), and the compiler said CS0120. The async versions in MySql.Data aren't static, unlike the methods they mirror.
/health/ready said Unhealthy, and the log said with message '(null)'. No exception, and no reason. The real error is one request away: the EF Core check swallows it, and a normal request doesn't.
I put Kestrel:Limits:MaxRequestBodySize in appsettings.json, set to 1 MB, and a 2 MB request went straight through with no warning. Kestrel reads its endpoints from that section, but not its limits, so the setting looks right and does nothing.
Connect Timeout=0 looks as if it should mean "no limit", as it does for many timeouts. In MySql.Data, every pooled connection failed at once with Timeout expired, on a server with nothing else connected.
CREATE command denied to user 'inventory_app'@'172.23.0.1' for table '__EFMigrationsHistory' appeared even though that table already existed. It's what you get when dotnet ef database update runs as an app account that can only read and change rows: exactly how that account should be set up, and exactly why migrations need a different one.
Option not supported (Parameter 'def;sslmode') looked like a typo in an option name, but def was the end of my password. A ; ends a value in a connection string, so the driver read the rest of the password as a new option, and put it in the exception message. That message can end up in your logs.
User 'inventory_app' has exceeded the 'max_user_connections' resource (current value: 5) means the account has reached a limit on connections, and the pool tried to open one more. One account limit and one pool setting need to agree, and until they do, some requests fail.
