Fix RST grammar errors in CHANGES.rst

[aisk]

Summary by CodeRabbit

• Bug Fixes
  • Fixed Cython build errors.
  • Addressed binary type ID issues in serialization.
  • Resolved socket leaks in asynchronous support.
  • Various other bug fixes across different releases.

[coderabbitai]

Walkthrough

The recent updates to Thriftpy focus on enhancing stability and performance. Key improvements include the resolution of Cython build errors, fixing serialization issues related to binary type IDs, and eliminating socket leaks in asynchronous operations. Additionally, a variety of bugs have been addressed, further refining the user experience and reliability of the library.

Changes

Files/Components	Change Summary
Cython-related	Fixed build errors
Serialization	Addressed binary type ID issues
Asynchronous support	Resolved socket leaks
Various components	Bug fixes across different releases

🐇✨
In the world of code, where rabbits hop,
Thriftpy's updates make our hearts stop.
With bugs squashed and leaks no more,
Our binary dances, our spirits soar.
So here’s to the devs, with their magic so bright,
In the glow of their screens, they bring dreams to light.
🌟🐰

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 2

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5784039 and 315f516.

Files selected for processing (1)

• CHANGES.rst (3 hunks)

Additional comments: 3

CHANGES.rst (3)

• 10-10: The release date format is consistent and correctly documented. No RST grammar errors are found in the release date lines.
• 40-40: The bullet points listing the changes for each version are correctly formatted with a dash and a space. This is consistent with RST syntax for unordered lists.
• 40-40: Hyperlinks to pull requests are correctly formatted using the RST syntax for links. The use of backticks and underscores is appropriate for creating clickable links.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ad0d38e and 0c12b4e.

Files selected for processing (1)

• CHANGES.rst (3 hunks)

Files skipped from review as they are similar to previous changes (1)

• CHANGES.rst

[aisk]

Since this is a trival change which fixed the grammar error in changelog, I'll merge it after the CI passed. cc @ethe