-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 Breaking Changes #739
Comments
Hello @michaelhelmick , |
Correct! The only place I could find that MySQL is no longer started by default was the blog post disconnected from documentation. Would be super helpful!
…Sent from my iPhone
On Apr 20, 2020, at 6:00 AM, Maxim Lobanov ***@***.***> wrote:
Hello @michaelhelmick ,
Am I right that your proposal is about updating documentation to include information that MySQL service is not enabled by default and instructions how it can be enabled. Please correct me if I am wrong
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Documentation has been successfully updated in scope of this PR. Changes were merged and will be delivered to all VMs in a week. |
Documentation has been successfully updated. All changes are delivered to VMs. Feel free to contact if you have any issues. |
Describe the bug
Not so much a bug, but more of a clearer description on how to use software on the OS.
Area for Triage:
Question
Question, Bug, or Feature?:
Question
Virtual environments affected
Expected behavior
mysql to work out of the box without starting
Actual behavior
I looked across the community for solutions (including adding
services
, updating ports, trying different hosts, and it ended up being that mysql doesn't start automatically anymore (via https://github.blog/changelog/2020-02-21-github-actions-breaking-change-ubuntu-virtual-environments-will-no-longer-start-the-mysql-service-automatically/) I think it would be appreciated if that was noted somewhere other than a blog post.The text was updated successfully, but these errors were encountered: