Bug #104685 Mysql.Data Nuget Package gets Bad value for ai_flags when connected via sockets
Submitted: 23 Aug 2021 1:07 Modified: 27 Sep 2021 12:54
Reporter: Kevin Connell Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:8.0.26 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: dotnet

[23 Aug 2021 1:07] Kevin Connell
Description:
The package Mysql.Data in nuget version 8.0.26 has a breaking change that does not allow connecting to mysql instances in the google cloud.    Stack trace is here: https://i.imgur.com/s7oMuGN.png

How to repeat:
Attempt to connect to google cloud mysql from google cloud run using a connection string like so:

var connectionString = new MySqlConnectionStringBuilder()
                {
                    // The Cloud SQL proxy provides encryption between the proxy and instance.
                    SslMode = MySqlSslMode.None,

                    Server = String.Format("{0}/{1}", dbSocketDir, instanceConnectionName),
                    UserID = Environment.GetEnvironmentVariable("DB_USER"),
                    Password = Environment.GetEnvironmentVariable("DB_PASS"),
                    Database = Environment.GetEnvironmentVariable("DB_NAME"),
                    ConnectionProtocol = MySqlConnectionProtocol.UnixSocket,
                    ConnectionTimeout = 300,
                    DefaultCommandTimeout = 5000,
                    //  Keepalive = 30

                };
[27 Aug 2021 12:54] MySQL Verification Team
Hello Kevin Connell,

Thank you for the bug report.
May I request you to please provide a complete test case to reproduce this issue at our end? If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. 

Regards,
Ashwini Patil
[28 Sep 2021 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[15 Jun 2022 20:17] António Pestana
I'm experiencing the same problem in version 8.0.29. I downgraded versions until it started working (8.0.23).