build(deps): bump kotlinx-io from 0.4.0 to 0.5.1

[dependabot]

Bumps kotlinx-io from 0.4.0 to 0.5.1.
Updates org.jetbrains.kotlinx:kotlinx-io-core from 0.4.0 to 0.5.1

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-io-core's releases.

v0.5.1

Bugfixes

• Fixed a bug in segment pool implementation affecting a second level pool uses.

v0.5.0

Features

• Provided an API allowing direct access to Buffer and Segment internals #135, #166

  The API is unsafe, delisted from public docs and requires explicit opt-in. It's recommended to avoid this API unless you're working on integration with other APIs (like, java.nio or io_uring, for example).

• Improved the way segment pooling is working on JVM #352

  Now sharing a segment won't make an original segment and all its copies recyclable. Instead, the last remaining copy will be placed back into the pool when recycled. Segments are no longer allocated or lost when taking or recycling a segment from a pool under a high contention due to concurrent requests. The size of the segment pool on the JVM could now be statically configured by setting a system property kotlinx.io.pool.size.bytes.

Thanks to @​bjhham, @​e5l, @​lppedd, @​qwwdfsad, @​shanshin, and @​whyoleg for their participation in this release release!

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-io-core's changelog.

0.5.1

Published 15 July 2024

Bugfixes

• Fixed a bug in segment pool implementation affecting a second level pool uses.

0.5.0

Published 12 July 2024

Features

• Provided an API allowing direct access to Buffer and Segment internals #135, #166

  The API is unsafe, delisted from public docs and requires explicit opt-in. It's recommended to avoid this API unless you're working on integration with other APIs (like, java.nio or io_uring, for example).

• Improved the way segment pooling is working on JVM #352

  Now sharing a segment won't make an original segment and all its copies recyclable. Instead, the last remaining copy will be placed back into the pool when recycled. Segments are no longer allocated or lost when taking or recycling a segment from pool under a high contention due to concurrent requests. Size of the segment pool on the JVM could now be statically configured by setting a system property kotlinx.io.pool.size.bytes.

Commits

• 8a8d1d5 Release 0.5.1
• 2e3b7d8 Fixed L2-pool-related typos
• c2ff370 Release 0.5.0
• be2bfca SegmentPool improvements (#352)
• 3eb8117 Correctly split head segment (#350)
• cc82d10 Update BCV to 0.15.0-Beta.3 and regenerate dumps (#349)
• 2e2f71a Fix incorrect atomic updates (#348)
• 8d9c36c Minor cleanup: postpone nullable ref null-check
• 31a40ed [Unsafe API 3/5] Implement Unsafe API to iterate over segments and access its...
• 72fa4ee [PR 2/5] Introduce unsafe API for bulk read/write ops (#334)
• Additional commits viewable in compare view

Updates org.jetbrains.kotlinx:kotlinx-io-bytestring from 0.4.0 to 0.5.1

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-io-bytestring's releases.

v0.5.1

Bugfixes

• Fixed a bug in segment pool implementation affecting a second level pool uses.

v0.5.0

Features

• Provided an API allowing direct access to Buffer and Segment internals #135, #166

  The API is unsafe, delisted from public docs and requires explicit opt-in. It's recommended to avoid this API unless you're working on integration with other APIs (like, java.nio or io_uring, for example).

• Improved the way segment pooling is working on JVM #352

  Now sharing a segment won't make an original segment and all its copies recyclable. Instead, the last remaining copy will be placed back into the pool when recycled. Segments are no longer allocated or lost when taking or recycling a segment from a pool under a high contention due to concurrent requests. The size of the segment pool on the JVM could now be statically configured by setting a system property kotlinx.io.pool.size.bytes.

Thanks to @​bjhham, @​e5l, @​lppedd, @​qwwdfsad, @​shanshin, and @​whyoleg for their participation in this release release!

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-io-bytestring's changelog.

0.5.1

Published 15 July 2024

Bugfixes

• Fixed a bug in segment pool implementation affecting a second level pool uses.

0.5.0

Published 12 July 2024

Features

• Provided an API allowing direct access to Buffer and Segment internals #135, #166

  The API is unsafe, delisted from public docs and requires explicit opt-in. It's recommended to avoid this API unless you're working on integration with other APIs (like, java.nio or io_uring, for example).

• Improved the way segment pooling is working on JVM #352

  Now sharing a segment won't make an original segment and all its copies recyclable. Instead, the last remaining copy will be placed back into the pool when recycled. Segments are no longer allocated or lost when taking or recycling a segment from pool under a high contention due to concurrent requests. Size of the segment pool on the JVM could now be statically configured by setting a system property kotlinx.io.pool.size.bytes.

Commits

• 8a8d1d5 Release 0.5.1
• 2e3b7d8 Fixed L2-pool-related typos
• c2ff370 Release 0.5.0
• be2bfca SegmentPool improvements (#352)
• 3eb8117 Correctly split head segment (#350)
• cc82d10 Update BCV to 0.15.0-Beta.3 and regenerate dumps (#349)
• 2e2f71a Fix incorrect atomic updates (#348)
• 8d9c36c Minor cleanup: postpone nullable ref null-check
• 31a40ed [Unsafe API 3/5] Implement Unsafe API to iterate over segments and access its...
• 72fa4ee [PR 2/5] Introduce unsafe API for bulk read/write ops (#334)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

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

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.

[github-actions]

🔄 Baseline update started...

[github-actions]

✅ Baseline updated.