Skip to content
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 9.1 is released #1159

Merged
merged 2 commits into from
Oct 21, 2024
Merged

MySQL 9.1 is released #1159

merged 2 commits into from
Oct 21, 2024

Conversation

shogo82148
Copy link
Owner

@shogo82148 shogo82148 commented Oct 21, 2024

Summary by CodeRabbit

  • New Features

    • Expanded testing capabilities with additional operating systems (windows-2022, windows-2019) and a new MySQL version (9.1) in the testing matrix.
    • Updated version list to include MySQL version 9.1.0 and reflect recent updates to existing versions.
  • Bug Fixes

    • Streamlined installation process by omitting unnecessary Program Database (.pdb) files during builds for Windows targets.

Copy link

coderabbitai bot commented Oct 21, 2024

Walkthrough

The pull request introduces modifications to the testing workflow and installation process for MySQL versions. The .github/workflows/test.yml file is updated to include additional operating systems and a new MySQL version in the testing matrix. Simultaneously, several patches streamline the installation of Program Database (.pdb) files by removing their installation logic from the build process for Windows targets across multiple MySQL versions. Additionally, the versions/mysql.json file is updated to reflect new and modified MySQL version entries.

Changes

File Path Change Summary
.github/workflows/test.yml Updated test job to include windows-2022, windows-2019 and added MySQL version 9.1.
patches/mysql/8.0.40/skip-install-pdb.patch Removed installation logic for .pdb files in install_macros.cmake and Plugin.cmake.
patches/mysql/8.4.3/skip-install-pdb.patch Removed installation logic for .pdb files in install_macros.cmake and Plugin.cmake.
patches/mysql/9.1.0/skip-install-pdb.patch Removed installation logic for .pdb files in install_macros.cmake and Plugin.cmake.
versions/mysql.json Added version 9.1.0, updated 8.4.2 to 8.4.3, and 8.0.39 to 8.0.40.

Possibly related PRs

  • MySQL v8.0.38 is released #1086: The changes in this PR involve modifications to the installation process for .pdb files in the cmake/install_macros.cmake and Plugin.cmake files, which is relevant as the main PR also includes updates related to MySQL version 9.1 in the testing matrix.

Poem

In the warren where we play,
New tests come out to frolic and sway.
Windows join the fun, oh what a sight,
With MySQL 9.1 shining bright!
No more .pdb files, we hop with glee,
Simplified paths, as happy as can be! 🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (10)
patches/mysql/8.0.40/skip-install-pdb.patch (3)

8-38: Approved: Removal of .pdb file installation logic

The removal of .pdb file installation logic is appropriate given the stated reason. This change will help reduce the size of the build artifacts, which is beneficial for GitHub Actions workflows.

Consider expanding the comment slightly for better clarity:

-# .pdb files are too large to use in GitHub Actions.
-# so skip installing
+# .pdb files are too large to use efficiently in GitHub Actions,
+# so we're skipping their installation to reduce artifact size.

41-62: Approved: Removal of .pdb file installation for .exe and .dll files

The removal of .pdb file installation logic for .exe and .dll files is consistent with the changes made to the INSTALL_DEBUG_SYMBOLS macro. This further contributes to reducing the size of build artifacts.

Consider adding a brief comment explaining the removal, similar to the one added in the INSTALL_DEBUG_SYMBOLS macro:

 FUNCTION(INSTALL_DEBUG_TARGET target)
   IF(MSVC)
     ...
   ENDIF()
 
+  # .pdb file installation removed to reduce artifact size for GitHub Actions
 ENDFUNCTION()

1-78: Summary: Comprehensive removal of .pdb file installation

This patch successfully removes the installation of .pdb files across different parts of the MySQL 8.0.40 build system. The changes are consistent and well-explained, contributing to the goal of reducing artifact size for GitHub Actions workflows.

Key points:

  1. Removed .pdb file installation from INSTALL_DEBUG_SYMBOLS macro
  2. Removed .pdb file installation for .exe and .dll files in INSTALL_DEBUG_TARGET function
  3. Removed .pdb file installation for harness plugin in Plugin.cmake

These changes will result in smaller build artifacts, which is beneficial for CI/CD processes, especially in GitHub Actions environments.

Consider documenting this change in a changelog or release notes, as it may affect developers who rely on .pdb files for debugging purposes in Windows environments.

patches/mysql/8.4.3/skip-install-pdb.patch (3)

8-37: Approved: Removal of .pdb file installation

The removal of .pdb file installation is a good optimization for GitHub Actions environments where space is a concern. This change simplifies the installation process for Windows targets.

Consider updating the macro name to reflect its new behavior, as it no longer installs debug symbols. For example:

-MACRO(INSTALL_DEBUG_SYMBOLS target)
+MACRO(SKIP_DEBUG_SYMBOLS_INSTALLATION target)

This would make the macro's purpose clearer to other developers.


45-62: Approved: Consistent removal of .pdb file installation

The removal of .pdb file installation for .exe and .dll files is consistent with the changes made in the INSTALL_DEBUG_SYMBOLS macro. This further simplifies the installation process and reduces the overall size of the installation.

Consider adding a comment explaining why this block was removed, similar to the comment added in the INSTALL_DEBUG_SYMBOLS macro. For example:

# .pdb files are too large to use in GitHub Actions, so skip installing

This would provide context for future developers who might wonder why this functionality was removed.


1-79: Summary: Optimization of installation process by removing .pdb files

This patch consistently removes the installation of .pdb files across different parts of the project (main installation, debug targets, and router component). This change:

  1. Reduces the overall size of the installation, which is beneficial for GitHub Actions environments.
  2. Simplifies the installation process for Windows targets.
  3. Maintains a uniform approach to handling debug symbols across the project.

These changes align well with the goal of optimizing the build and installation process for CI/CD environments.

Consider documenting this change in a changelog or release notes, as it might affect developers who rely on .pdb files for debugging. You may also want to provide alternative ways for developers to access debug symbols if needed, such as separate debug symbol packages or a symbol server.

patches/mysql/9.1.0/skip-install-pdb.patch (4)

8-38: Approved: Removal of .pdb file installation

The removal of .pdb file installation is a reasonable optimization for GitHub Actions, as these files can be quite large. This change will help reduce build times and artifact sizes.

Consider adding a more detailed comment or documentation explaining the implications of this change, such as:

# .pdb files are too large to use in GitHub Actions.
# Skipping installation to reduce build times and artifact sizes.
# Note: This may impact debugging capabilities in Windows environments.

45-63: Approved: Consistent removal of .pdb file installation

This change aligns with the earlier modification to skip .pdb file installation, ensuring consistency throughout the build process.

Consider adding a brief comment explaining why this block was removed, similar to the one added in the INSTALL_DEBUG_SYMBOLS macro. For example:

# Removed .pdb file installation for Windows to reduce build artifact size

This will help future maintainers understand the reasoning behind this change.


70-79: Approved: Removal of .pdb file installation for harness plugin

This change is consistent with the earlier modifications to skip .pdb file installation, ensuring that the harness plugin follows the same optimization strategy.

Consider adding a brief comment explaining the removal of this block, similar to the suggestions for the other files. For example:

# Removed .pdb file installation for harness plugin to reduce build artifact size

This will maintain consistency in documentation across the changes.


1-79: Summary: Consistent removal of .pdb file installation

This patch successfully removes the installation of .pdb files across multiple cmake files, which will significantly reduce the size of build artifacts for GitHub Actions. The changes are consistent and well-implemented.

Consider the following recommendations:

  1. Add a comment in the main README or documentation explaining this change and its implications for debugging on Windows platforms.
  2. Ensure that there's a way to optionally generate .pdb files for local development and debugging purposes, perhaps through a cmake option.
  3. Update any relevant documentation or guides that may reference .pdb files or Windows debugging processes.

These steps will help maintain the project's usability across different environments while optimizing for CI/CD processes.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 1466a42 and e8c0fe2.

📒 Files selected for processing (5)
  • .github/workflows/test.yml (1 hunks)
  • patches/mysql/8.0.40/skip-install-pdb.patch (1 hunks)
  • patches/mysql/8.4.3/skip-install-pdb.patch (1 hunks)
  • patches/mysql/9.1.0/skip-install-pdb.patch (1 hunks)
  • versions/mysql.json (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • versions/mysql.json
🧰 Additional context used
🔇 Additional comments (3)
patches/mysql/8.0.40/skip-install-pdb.patch (1)

69-78: Approved: Removal of .pdb file installation for harness plugin

The removal of .pdb file installation for the harness plugin is consistent with the changes made in other parts of the patch. This change contributes to the overall goal of reducing artifact size and streamlining the installation process.

patches/mysql/8.4.3/skip-install-pdb.patch (1)

70-79: Approved: Consistent removal of .pdb file installation for router component

The removal of .pdb file installation for the router component is consistent with the changes made in other parts of the patch. This maintains a uniform approach to handling debug symbols across the project.

.github/workflows/test.yml (1)

46-46: LGTM! Verify MySQL 9.1 availability in the action.

The addition of MySQL 9.1 to the test matrix is appropriate and aligns with the PR objective. This ensures that the action is tested against the latest MySQL version.

To ensure that MySQL 9.1 is properly supported by the action, please run the following verification script:

@shogo82148 shogo82148 changed the title Mysql9.1 is released MySQL 9.1 is released Oct 21, 2024
@shogo82148 shogo82148 merged commit 7ec6831 into main Oct 21, 2024
271 checks passed
@shogo82148 shogo82148 deleted the mysql9.1-is-released branch October 21, 2024 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant