update decodeless_allocator default

[pknowles]

Summary by CodeRabbit

• Chores
  • Updated dependency decodeless_allocator to a new Git commit version.

[coderabbitai]

Walkthrough

The pull request involves a specific update to the CMakeLists.txt file for the decodeless_writer project. The modification focuses on changing the Git tag for the decodeless_allocator dependency from one commit hash to another, effectively updating the version of the dependency being used. This change does not alter the overall project structure or dependency management approach.

Changes

File	Change Summary
CMakeLists.txt	Updated decodeless_allocator dependency Git tag from 772bcb7e0c0f5bbdf3358395046e995a9d6c1ffb to 976a34bd7f9784839dd9bba05262001a498f5ce4

Poem

🐰 A cmake tale of version dance,
Allocator's tag takes a new stance,
From one hash to another we leap,
Dependencies update, quietly keep,
A rabbit's build, precise and neat! 🔧

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6cd674f and 0da9e98.

📒 Files selected for processing (1)

• CMakeLists.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build (windows-latest, Release, cl)
• GitHub Check: build (windows-latest, Debug, cl)

🔇 Additional comments (1)

CMakeLists.txt (1)

25-25: Verify the allocator update and document the changes.

Let's verify the commit and understand the changes between versions.

Please document in the PR description:

1. What changes are included in the new allocator version
2. Why this update is needed
3. Any potential breaking changes or compatibility issues

✅ Verification successful

✓ Allocator update is a safe compatibility fix

The update improves Visual Studio 2019 compatibility by fixing template-related compilation issues, with no behavioral changes. The detailed commit message sufficiently documents the changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the commit exists and check the changes between versions

# Check if the new commit exists in the repository
gh api repos/decodeless/allocator/commits/976a34bd7f9784839dd9bba05262001a498f5ce4 --jq '.sha'

# Get the commit message to understand the changes
gh api repos/decodeless/allocator/commits/976a34bd7f9784839dd9bba05262001a498f5ce4 --jq '.commit.message'

# Compare the commits to see the scope of changes
gh api repos/decodeless/allocator/compare/772bcb7e0c0f5bbdf3358395046e995a9d6c1ffb...976a34bd7f9784839dd9bba05262001a498f5ce4 --jq '.commits[].commit.message'

Length of output: 1806

---

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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 or @coderabbitai title 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.