Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: deleting incorrect repo path #426

Merged
merged 3 commits into from
Jan 10, 2025

Conversation

hajdul88
Copy link
Contributor

@hajdul88 hajdul88 commented Jan 10, 2025

Summary by CodeRabbit

  • New Features

    • Added dynamic repository download functionality for evaluation purposes
    • Introduced utility methods for handling GitHub repository retrieval
  • Chores

    • Updated repository path handling in evaluation scripts

Copy link
Contributor

coderabbitai bot commented Jan 10, 2025

Walkthrough

The changes involve modifications to the evals/eval_swe_bench.py file, specifically in how repository paths are obtained. The update introduces a dynamic method for downloading GitHub repositories using a new function from evals.eval_utils. Instead of using a hardcoded local path, the code now uses download_github_repo to retrieve the repository path, making the repository retrieval process more flexible and programmatic.

Changes

File Change Summary
evals/eval_swe_bench.py - Added import for download_github_repo and retrieved_edges_to_string from evals.eval_utils
- Replaced hardcoded repo path with dynamic download_github_repo() method
evals/eval_utils.py - Added new methods download_github_repo()
- Added new methods retrieved_edges_to_string()

Poem

🐰 A Rabbit's Repo Rhapsody 🌿

Paths no longer static and stale,
Dynamic downloads now set sail!
GitHub repos dance with glee,
Flexible fetching, wild and free!
CodeRabbit's magic takes the stage! 🚀

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

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

🧹 Nitpick comments (1)
evals/eval_swe_bench.py (1)

17-17: Remove unused import retrieved_edges_to_string

The retrieved_edges_to_string function is imported but never used in this file. Consider removing it to maintain clean imports.

-from evals.eval_utils import download_github_repo, retrieved_edges_to_string
+from evals.eval_utils import download_github_repo
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f694ca2 and e2ad54d.

📒 Files selected for processing (1)
  • evals/eval_swe_bench.py (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (18)
  • GitHub Check: run_simple_example_test / test
  • GitHub Check: run_dynamic_steps_example_test / test
  • GitHub Check: run_notebook_test / test
  • GitHub Check: run_notebook_test / test
  • GitHub Check: run_notebook_test / test
  • GitHub Check: run_multimedia_example_test / test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: profiler
  • GitHub Check: docker-compose-test
  • GitHub Check: Publish Cognee Docker image
🔇 Additional comments (1)
evals/eval_swe_bench.py (1)

37-37: Verify removal of all hardcoded repository paths

Since this PR aims to fix incorrect repository paths, let's verify that all instances have been addressed.

✅ Verification successful

All hardcoded repository paths have been addressed

The verification confirms that the modified line in evals/eval_swe_bench.py was the only instance of hardcoded repository paths that needed to be addressed. Other path traversal patterns found in the codebase are either comments or legitimate use cases unrelated to repository paths.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for potential hardcoded repository paths in the codebase
echo "Searching for potential hardcoded repository paths..."
rg -i "RAW_GIT_REPOS|repo_path\s*=\s*['\"]" --type py

# Search for path traversal patterns
echo "Searching for path traversal patterns..."
rg -i "\.\./" --type py

Length of output: 743

@@ -33,12 +34,11 @@ def check_install_package(package_name):


async def generate_patch_with_cognee(instance):
"""repo_path = download_github_repo(instance, "../RAW_GIT_REPOS")"""
repo_path = download_github_repo(instance, "../RAW_GIT_REPOS")
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

Improve repository path handling and add error handling

Several improvements needed for the repository download:

  1. The hardcoded relative path "../RAW_GIT_REPOS" is fragile and traverses outside the package directory. Consider:

    • Using an absolute path from a configuration
    • Using a path within the package directory
    • Using a temporary directory
  2. Add error handling for download failures

Example implementation:

-    repo_path = download_github_repo(instance, "../RAW_GIT_REPOS")
+    try:
+        # Option 1: Use package directory
+        from pathlib import Path
+        package_root = Path(__file__).parent.parent
+        repos_dir = package_root / "data" / "repos"
+        repo_path = download_github_repo(instance, repos_dir)
+        
+        # Option 2: Use temporary directory
+        # import tempfile
+        # with tempfile.TemporaryDirectory() as repos_dir:
+        #     repo_path = download_github_repo(instance, repos_dir)
+    except Exception as e:
+        raise RuntimeError(f"Failed to download repository: {e}")

Committable suggestion skipped: line range outside the PR's diff.

@Vasilije1990 Vasilije1990 merged commit e9c40ed into dev Jan 10, 2025
27 of 41 checks passed
@Vasilije1990 Vasilije1990 deleted the feature/cog-971-preparing-swe-bench-run branch January 10, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants