Temporarily lock clang-format to v18.x to resolve lint failures; Update to latest commit of CLP core (fixes #70).

[LinZhihao-723]

References

Description

This PR:

• Temporary locking clang-format to version 18 to work around (lint workflow failed due to clang-format warnings #71)
• Update to the latest commit of CLP core to apply the fix (Windows Wheel Build Failing #70)

Validation performed

• Ensure local build worked.
• Ensure workflow all passed.

Summary by CodeRabbit

• Chores
  • Updated the version specification for the clang-format dependency to ensure compatibility.
  • Updated the commit hash for a subproject, reflecting its latest state.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from aef6e9c to 9b86d60.

Walkthrough

The pull request includes updates to the requirements-dev.txt file, specifically changing the version specification for the clang-format dependency from a minimum version (>=18.1.5) to a compatible version (~=18.1). Additionally, there is an update to the commit hash for a subproject within the src/clp directory, reflecting a change in the subproject's version or state without further context on the modifications.

Changes

File	Change Summary
requirements-dev.txt	Updated clang-format version from >=18.1.5 to ~=18.1.
src/clp	Updated subproject commit hash from 9dabb926dfc6dd9f4274052634a4ece81f322f16 to 65b231b66230e3a542cfefbdd2acec00fa7f6ca9.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant System
    User->>System: Request to update dependencies
    System->>System: Check current versions
    System->>System: Update clang-format version
    System->>User: Confirm version updated to ~=18.1
    
    User->>System: Request subproject update
    System->>System: Update subproject commit hash
    System->>User: Confirm subproject updated

Loading

---

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 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.

[kirkrodrigues]

For the PR title, how about:

Temporarily lock clang-format to v18.x to resolve lint failures; Update to latest commit of CLP core (fixes #70).