Fixes for Common Issues and Errors
View All Tags
I ran SHOW PROCESSLIST in MySQL 9.7 to see who was connected, and the result ended with 1 warning. SHOW WARNINGS named it: Warning 1287, the old implementation behind SHOW PROCESSLIST is deprecated. Querying the Performance Schema's processlist table directly gives the same list, without the warning.
I changed a password in my .env file, restarted MySQL with Docker Compose, and MySQL rejected the new password with ERROR 1045 (28000): Access denied. The container had the new value, but MySQL was still expecting the old one. This post shows why that happens with the official MySQL image, and how I fixed it without deleting any data.
I typed SELECT 'café' into the mysql client inside the official MySQL Docker container, and the client showed 'caf'. The é never appeared on screen and never reached MySQL, and there was no error at all. The container runs without a locale, so the client only accepts plain ASCII. One extra flag on docker compose exec fixes it.
I continued a conversation the way many chat clients do — by sending the whole conversation again — and the Microsoft Agent Framework agent read its first question and its own first answer twice. The answer still looked fine, which is what makes this easy to miss. Foundry's stored input showed the duplicates, and sending only the new message fixed it.
I gave a Microsoft Agent Framework agent a session store so it would remember conversations, and every request started failing with a 500: Agent isolation key is required but was not provided by the configured AgentIsolationKeyProvider. I had configured no provider at all. The default store wanted to know who was calling, and my API had no way to tell it.
My Azure CLI query asked for three fields — type, role and text — and --output table printed only two columns. The type column had vanished without a warning. The Azure CLI hides that key in tables on purpose, and renaming it in the query brings it back.
Microsoft's page on ASP.NET Core environments says dotnet run -e Staging sets the environment. I ran it, and my API started in Development anyway, with no error and no warning. -e sets an environment variable, so it needs a name and a value: -e ASPNETCORE_ENVIRONMENT=Staging does what the short form promises.
dotnet build normally ends with a compact Build succeeded in 0.9s. In one terminal it printed the old format instead — Build succeeded., 0 Warning(s), 0 Error(s), Time Elapsed. The build was fine. The display wasn't what I expected, because on macOS and Linux .NET decides how to draw its output from the TERM environment variable, and mine was empty.
A manager opened a shared app in a new trial environment and got You can't open apps in this environment. You are not a member of the environment's security group. He was a member. The cause is how trial environments add people, and the fix is to add them to the environment yourself, or have them open the app again.
I created a Microsoft Entra group team, ticked Basic User, selected Save and got a success message. When I opened the team's roles again, nothing was ticked. Selecting Save in the roles pane only opens a confirmation, and the role is assigned when you select Save a second time, in that confirmation.
