Skip to content

Conversation

@davidlion
Copy link
Member

@davidlion davidlion commented May 16, 2025

Description

Currently there is a weird case where if all build, install, and source directory paths are specified then the required parameter WORK_DIR is unused.

Rather than adding logic to check the combination of variables, we're simply removing the these directory paths from being optional parameters. Since utils:cmake:install-remote-tar requires a working CMake project there was no reason to override these directories and existing use cases were already just letting the directories default to be inside WORK_DIR.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

Tested locally with log-surgeon.

Summary by CodeRabbit

  • Chores
    • Updated internal directory path handling for remote installation tasks to use consistent default locations.

@davidlion davidlion requested a review from a team as a code owner May 16, 2025 22:45
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 16, 2025

Walkthrough

The change updates the install-remote-tar task in exports/taskfiles/utils/cmake.yaml by removing conditional defaulting logic for directory variables and replacing them with fixed path templates based on WORK_DIR and NAME. It also removes commented documentation lines describing the previous default behaviour.

Changes

File(s) Change Summary
exports/taskfiles/utils/cmake.yaml Removed commented documentation for directory parameter defaults; replaced conditional default logic with fixed path templates for BUILD_DIR, INSTALL_PREFIX, and SOURCE_DIR.

Possibly related PRs

Suggested reviewers

  • kirkrodrigues

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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
Contributor

@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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c19656b and cd71fec.

📒 Files selected for processing (1)
  • exports/taskfiles/utils/cmake.yaml (1 hunks)

Comment on lines +170 to +172
BUILD_DIR: "{{.WORK_DIR}}/{{.NAME}}-build"
INSTALL_PREFIX: "{{.WORK_DIR}}/{{.NAME}}-install"
SOURCE_DIR: "{{.WORK_DIR}}/{{.NAME}}-src"
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Clarify fixed directory paths and update documentation.
We’ve removed the ability to override BUILD_DIR, INSTALL_PREFIX, and SOURCE_DIR in favour of always placing them under WORK_DIR. Please update the task’s doc comments (and any examples/README) to remove references to these as overridable parameters, and consider adding an inline note here to explain that these paths are now fixed.

🤖 Prompt for AI Agents
In exports/taskfiles/utils/cmake.yaml around lines 170 to 172, the variables
BUILD_DIR, INSTALL_PREFIX, and SOURCE_DIR are now fixed to be under WORK_DIR and
cannot be overridden. Update the task's documentation comments and any related
examples or README files to remove mentions of these as overridable parameters.
Additionally, add an inline comment near these lines explaining that these
directory paths are fixed and always relative to WORK_DIR.

@davidlion davidlion requested a review from kirkrodrigues May 16, 2025 22:59
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.

2 participants