fix: resolve issue with repo in swe bench evals

[dexters1]

Summary by CodeRabbit

• New Features
  • Introduced dynamic repository path retrieval for evaluation process
  • Added capability to download GitHub repositories programmatically

[coderabbitai]

Walkthrough

The pull request modifies the evals/eval_swe_bench.py file to dynamically obtain the repository path using the download_github_repo function from the eval_utils module. Instead of using a hardcoded path, the code now calls the function with an instance and a base directory, allowing for more flexible repository retrieval during evaluation processes.

Changes

File	Change Summary
evals/eval_swe_bench.py	Replaced hardcoded repo_path assignment with dynamic download_github_repo() function call

Possibly related PRs

• Fix: deleting incorrect repo path #426: Involves similar modifications to the download_github_repo function and repo_path assignment in the generate_patch_with_cognee function

Suggested reviewers

• Vasilije1990

Poem

🐰 A rabbit's tale of code so bright,
Paths now dance with dynamic might!
No more hardcoded strings to bind,
Flexibility leaps, leaving static behind
Repos download with agile grace 🚀

---

📜 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 b888597 and efe3360.

📒 Files selected for processing (1)

• evals/eval_swe_bench.py (2 hunks)

🔇 Additional comments (2)

evals/eval_swe_bench.py (2)

17-17: LGTM!

The import of download_github_repo from eval_utils is appropriately placed and aligns with the PR's objective.

---

37-37: 🛠️ Refactor suggestion

Consider improving path handling and error handling.

While the dynamic repo path is an improvement over hardcoding, there are some concerns:

1. The relative path "../RAW_GIT_REPOS" may fail depending on the working directory. Consider using an absolute path or environment variable.
2. No error handling for potential download failures.

Here's a suggested improvement:

-    repo_path = download_github_repo(instance, "../RAW_GIT_REPOS")
+    try:
+        base_dir = os.getenv("RAW_GIT_REPOS_DIR", os.path.join(os.path.dirname(__file__), "../RAW_GIT_REPOS"))
+        repo_path = download_github_repo(instance, base_dir)
+        if not repo_path:
+            raise ValueError("Failed to download repository")
+    except Exception as e:
+        raise RuntimeError(f"Failed to setup repository: {str(e)}")

Let's verify the current usage of relative paths:

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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