Skip to content

Conversation

coodos
Copy link
Contributor

@coodos coodos commented Aug 26, 2025

Description of change

Issue Number

Type of change

  • Breaking (any change that would cause existing functionality to not work as expected)
  • New (a change which implements a new feature)
  • Update (a change which updates existing functionality)
  • Fix (a change which fixes an issue)
  • Docs (changes to the documentation)
  • Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

  • I have ensured that the CI Checks pass locally
  • I have removed any unnecessary logic
  • My code is well documented
  • I have signed my commits
  • My code follows the pattern of the application
  • I have self reviewed my code

Summary by CodeRabbit

  • Bug Fixes

    • Prevents updates to non-existent groups with a clear error.
    • Ensures group updates reliably trigger related workflows, including eVault creation and ename population.
  • Refactor

    • Streamlines update handling by operating on loaded entities to improve event consistency and downstream synchronization.
  • Chores

    • Reduces excessive debug logging for cleaner runtime logs.
    • Adds a short, delayed post-update sync to propagate newly created eVault data and related changes.

Copy link
Contributor

coderabbitai bot commented Aug 26, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The GroupService update path switches to read-modify-save with existence checks. The subscriber’s update handling is reworked to capture entity ID in beforeUpdate, rely on it in afterUpdate, switch certain updates to save-based flows, remove heuristic ID discovery, add a delayed post-update reload, and reduce logging.

Changes

Cohort / File(s) Summary
Group update path (read-modify-save)
platforms/group-charter-manager-api/src/services/GroupService.ts
Replaced direct repository.update + fetch with fetch-merge-save; added "Group not found" guard; ensures ORM events fire via save.
Subscriber update restructuring and log reductions
platforms/group-charter-manager-api/src/web3adapter/watchers/subscriber.ts
Capture ID in beforeUpdate; afterUpdate depends on captured ID or returns early; switch Group ename updates to findOne + save; add 20s delayed reload to trigger downstream handleChange; remove heuristic ID discovery and numerous debug logs; minor formatting.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Client
  participant GroupService
  participant Repo as GroupRepository (ORM)

  Client->>GroupService: updateGroup(id, partial)
  GroupService->>Repo: findOne(id)
  alt group exists
    GroupService->>GroupService: merge(existing, partial)
    GroupService->>Repo: save(merged)
    Repo-->>GroupService: savedGroup
    GroupService-->>Client: savedGroup
  else group missing
    GroupService-->>Client: throw "Group not found"
  end
Loading
sequenceDiagram
  autonumber
  participant ORM
  participant Sub as Subscriber
  participant Repo as Repository
  participant EV as eVault Service
  participant Down as Downstream Handler

  ORM-->>Sub: beforeUpdate(entity)
  Sub->>Sub: lastUpdateEntityId = entity.id (if present)

  ORM-->>Sub: afterUpdate(event)
  alt lastUpdateEntityId available
    Sub->>Repo: reload(entity by id with relations)
    alt Group with charter and no ename
      Sub->>EV: create eVault
      EV-->>Sub: ename assigned
      Sub->>Repo: findOne(id)
      Sub->>Repo: save(updated ename)  %% use save to trigger ORM
      Note over Sub: Delay ~20s
      Sub->>Repo: reload(id with relations)
      Sub->>Down: handleChange(updated group)
    else
      Sub->>Down: handleChange(reloaded entity)
    end
  else
    Sub-->>ORM: return (skip processing)
  end
Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Poem

I thump my paws—events align,
IDs in paw, the trails are fine.
Save, not update, the burrow hums,
Twenty ticks—ename becomes.
Logs grow quiet, flows run true—
Fresh carrots mapped, a tidy queue.
Hop, commit, and burrow through! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d009738 and 7a38128.

📒 Files selected for processing (2)
  • platforms/group-charter-manager-api/src/services/GroupService.ts (1 hunks)
  • platforms/group-charter-manager-api/src/web3adapter/watchers/subscriber.ts (2 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/charter-subscriber

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@coodos coodos merged commit b7bf95b into main Aug 26, 2025
0 of 4 checks passed
@coodos coodos deleted the fix/charter-subscriber branch August 26, 2025 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant