Skip to content

warp-core: edge reverse index for tick patch replay #152

Description

@flyingrobots

Tick patch replay currently needs to locate an existing edge by EdgeId when applying an UpsertEdge. Today this is implemented as an O(total_edges) scan across all outbound buckets.

Implement a reverse index in GraphStore (e.g., EdgeId -> from NodeId) so patch replay can migrate edges in O(bucket_edges) instead of O(total_edges).

Acceptance:

  • No behavioral change for state_root / commit_id semantics.
  • Clippy/tests/rustdoc gates remain green.
  • Tick patch apply no longer performs a full scan for UpsertEdge.

Activity

  1. coderabbitai commented on Dec 29, 2025

    @coderabbitai
    Contributor

    📝 CodeRabbit Plan Mode

    Generate an implementation plan and prompts that you can use with your favorite coding agent.

    • Create Plan
    Examples

    🔗 Similar Issues

    Related Issues

    🔗 Related PRs

    #150 - WarpTickPatchV1 delta patches + commit hash v2 [closed]

    👤 Suggested Assignees

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions