fix path for input_env_file

[Jooho]

Summary by CodeRabbit

• New Features

  • The script now sets an environment variable to store the original working directory when it is invoked.

• Bug Fixes

  • Improved handling of environment file paths by resolving them relative to the original working directory, ensuring more reliable file loading and clearer error messages.

[coderabbitai]

Walkthrough

An environment variable ORIGINAL_DIR is now exported in the loopy script to capture the initial working directory. The utility function for loading environment files in Python now resolves file paths relative to this variable, improving path handling. Error messages have been updated to reflect the resolved absolute path.

Changes

File(s)	Change Summary
loopy	Exports ORIGINAL_DIR environment variable with the current directory before changing to ROOT_PATH.
src/cli/commands/utils.py	Resolves env file path relative to ORIGINAL_DIR if set; updates error logging to use absolute path.

Poem

In burrows deep, where scripts may roam,
A bunny marks its starting home.
With ORIGINAL_DIR now set so neat,
Our env files never miss a beat.
Paths resolved, the journey's clear—
Hop on, code friends, the way is here! 🐇

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fcd0a8e and cf2d3c5.

📒 Files selected for processing (1)

• src/cli/commands/utils.py (2 hunks)

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

• src/cli/commands/utils.py

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

• GitHub Check: cluster-lifecycle-test (3.12)
• GitHub Check: cluster-test (3.12)
• GitHub Check: non-cluster-test (3.12)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e1d954e and fcd0a8e.

📒 Files selected for processing (2)

• loopy (1 hunks)
• src/cli/commands/utils.py (2 hunks)

🧰 Additional context used

🪛 Pylint (3.3.7)

src/cli/commands/utils.py

[refactor] 148-148: Redefining argument with the local name 'file'

(R1704)

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

• GitHub Check: cluster-test (3.12)
• GitHub Check: cluster-lifecycle-test (3.12)
• GitHub Check: non-cluster-test (3.12)

🔇 Additional comments (3)

loopy (1)

4-4: LGTM! Proper capture of original directory.

The export of ORIGINAL_DIR correctly captures the current working directory before changing to ROOT_PATH, enabling proper path resolution in downstream processes.

src/cli/commands/utils.py (2)

145-147: LGTM! Proper path resolution implementation.

The path resolution logic correctly uses the ORIGINAL_DIR environment variable with a sensible fallback to os.getcwd(), and properly constructs the absolute path for file operations.

---

158-158: LGTM! Improved error message.

The error message now correctly displays the resolved absolute path, making debugging easier for users.

[Jooho]

/approve
/lgtm