-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL 8.0 service not started in the latest Visual Studio 2022 image #3894
Comments
BAndysc
changed the title
MySQL 8.0 credentials in the latest Visual Studio 2022 image
MySQL 8.0 service not started in the latest Visual Studio 2022 image
Oct 31, 2023
Can you try after adding the following to your appveyor.yml config file.
|
Thanks for the answer, yup, this worked whereas |
4 tasks
NickCraver
added a commit
to DapperLib/Dapper
that referenced
this issue
Nov 13, 2023
Looks like the image was borked with MySQL 8 went in (because it's still trying to start 5.7), see appveyor/ci#3894.
NickCraver
added a commit
to DapperLib/Dapper
that referenced
this issue
Nov 13, 2023
Looks like the image was borked with MySQL 8 went in (because it's still trying to start 5.7), see appveyor/ci#3894.
huysentruitw
added a commit
to gantner-nv/Rebus.MySql
that referenced
this issue
Nov 14, 2023
bgrainger
added a commit
to mysql-net/MySqlConnector
that referenced
this issue
Dec 5, 2023
This mirrors changes other projects have made in response to this issue: appveyor/ci#3894
vadz
added a commit
to vadz/soci
that referenced
this issue
Dec 7, 2023
They don't have MySQL 5.7 any more but only 8.x and starting mysql service doesn't work any longer, so it has to be done manually, see appveyor/ci#3894
Giorgi
added a commit
to Giorgi/EntityFramework.Exceptions
that referenced
this issue
Dec 8, 2023
vadz
added a commit
to SOCI/soci
that referenced
this issue
Dec 11, 2023
They don't have MySQL 5.7 any more but only 8.x and starting mysql service doesn't work any longer, so it has to be done manually, see appveyor/ci#3894
phoenixdev9
pushed a commit
to phoenixdev9/Dapper
that referenced
this issue
Aug 18, 2024
Looks like the image was borked with MySQL 8 went in (because it's still trying to start 5.7), see appveyor/ci#3894.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest VS 2022 image includes MySQL 8.0 instead of 5.7, however it looks like the service is not working despite having
mysql
service enabled in the yml as per docs (or the credentials to the database were changed?) At least this command:used to work before and now
yields
The text was updated successfully, but these errors were encountered: