I believe that some small partners will encounter some unexplained problems in the process of using MySQL. After continuous efforts to investigate, they still cannot confirm what the situation is. At this time, you may need to check whether this phenomenon is a MySQL bug. . How to check MySQL bugs? How to submit a bug report? Can I contribute the code to solve this bug? In this article, I will answer you one by one.
MySQL officially provides a bug website, URL: https://bugs.mysql.com/ Through this website, you can find bugs, report bugs, and contribute code.
Retrieve bugs:
When you want to retrieve whether the problem encountered is reported as a bug, you can enter the relevant keywords on the right to retrieve it. This system also supports advanced search, which can be searched according to keywords, classification, status and other conditions. For specific items, please refer to the following figure:
The search result screen is as follows (search for "group replication" keyword):
At this time, you can check whether there are any results that are the same or similar to yours. Click on the item to see the details.
For those who often read the MySQL documentation, they often see some Bug# mentioned in the documentation, for example: "New FPROFILE_GENERATE and FPROFILE_USE CMake options are available for experimenting with profile guided optimization (PGO) with GCC. See the cmake /fprofile.cmake in a MySQL source distribution for information about using them. These options have been tested with GCC 8 and 9, and with Clang.
Enabling FPROFILE_USE also enables WITH_LTO (link time optimization). (Bug #30089834, Bug #96314, Bug #30133324, Bug #96410, Bug #30164113, Bug #96486)" You can enter these bug numbers to view the corresponding content, But please note that when you retrieve related bugs, there may be three types of results:
1. You do not have permission to access this bug: This situation is because this bug involves security-related issues. This type of bug information cannot be made public to prevent it from being exploited.
2. The bug does not exist or is stored in Oracle's internal system: usually the 8-digit number is stored in Oracle's internal bug system, mainly the bug proposed by Oracle's engineering team, and it is restricted to employees with internal permissions.
3. Bugs that can be disclosed: They are bugs that can be disclosed normally. Through this information, you can confirm the relevant content. If you think this bug has a great impact on you and want to fix it quickly, then please click "Affects Me" on the upper right. To reveal a secret, the number of clicks on this button will affect the repair priority of the engineering team. If you want to give priority to repair, you can ask your partner to do it together.
Report bug:
If you do not find the same situation as you, you can submit your own bug report.
The report form is as shown in the figure above. I need to be reminded. Please be sure to describe your bug in detail, including the version used, platform, and steps to reproduce. This information is very important. The MySQL team has someone responsible for confirming the bug. If the bug cannot be reproduced according to the information you provided, you need to supplement the relevant information and submit it again, which will affect the efficiency of the confirmation. After submission, the system will automatically send a bug status email, so you can know the relevant information the first time. Usually there will be a confirmed result within one day after submission.
Contributing Bug Code : After you retrieve a bug or submit a bug report, if you have a solution and can provide relevant code, the MySQL team hopes that you can contribute relevant code. At this time, you can contribute your code through the "Contributions" tab of the bug detail page. It should be noted that you need to sign the "Oracle Contribution Agreement (OCA)" before submitting the code. After review and modification by the engineering team, the code can be merged into the official code and upgraded with the upgrade of the MySQL version. So if you have modified code and better solutions, you are welcome to contribute your code. The contributed code can not only bring benefits to the open source enthusiasts, but also save you and your organization from upgrading and management in the future. For maintenance work, MySQL's engineering team will provide maintenance for your code, saving you and your organization a lot of engineering costs.
The above content is a concise introduction to the MySQL bug report.