potpie feat: Implement incremental update system with snapshot restore

Fixes: #221 /claim #221

Summary by CodeRabbit

Release Notes

New Features
- Introduced incremental update capabilities for project file parsing
- Added support for tracking and managing file changes in the knowledge graph
Improvements
- Enhanced error handling during file updates
- Implemented snapshot mechanism for graph state management
- Added logging for file change tracking and update processes
Performance
- Optimized file parsing with incremental update strategy
- Improved efficiency in handling project file modifications

Jan 26 '25 05:01 onyedikachi-david

Walkthrough

The pull request introduces an IncrementalUpdateService to enhance the knowledge graph update process by enabling partial, targeted updates instead of full graph reconstruction. The new service is integrated into the ParsingService, allowing for more efficient file updates by identifying and processing only changed components. The implementation supports change detection, relationship management, and selective inference generation, with built-in snapshot and rollback capabilities to ensure data consistency and error resilience.

Changes

File	Change Summary
`app/modules/parsing/graph_construction/parsing_service.py`	- Added optional `changed_files` parameter to `analyze_directory` method - Implemented incremental update logic with snapshot and fallback mechanisms - Added new `update_files` method for incremental file updates
`app/modules/parsing/incremental_update_service.py`	- New service class for managing incremental knowledge graph updates - Methods for file node retrieval, change tracking, and selective updates - Snapshot creation, restoration, and deletion functionality - Async methods for file and inference updates

Sequence Diagram

sequenceDiagram
    participant PS as ParsingService
    participant IUS as IncrementalUpdateService
    participant DB as Database
    participant Graph as Knowledge Graph

    PS->>IUS: analyze_directory(changed_files)
    IUS->>IUS: create_snapshot()
    IUS->>IUS: update_files(changed_files)
    IUS->>Graph: identify affected nodes
    IUS->>Graph: remove old nodes
    IUS->>Graph: create new nodes/relationships
    IUS->>IUS: update_inferences(affected_nodes)
    alt Update Successful
        IUS-->>PS: return update results
    else Update Failed
        IUS->>IUS: restore_snapshot()
        IUS-->>PS: return error
    end

Assessment against linked issues

Objective	Addressed	Explanation
Change Detection [#221]	✅
Relationship Management [#221]	✅
Inference Handling [#221]	✅
Performance Optimization [#221]	✅
Error Handling and Rollback [#221]	✅

Poem

🐰 Incremental updates hop and dance, Graph nodes shift with every glance, Snapshots guard our data's grace, Parsing service sets the pace, Knowledge grows, no time to waste! 🌱

✨ 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