Fix SpacesByOwner index update

[Pitasi]

I realized I broke the index even more with #423, now it gets completely wiped at every space update.

This PR finally fixes it, for good, I hope.

Summary by CodeRabbit

• New Features

  • Improved error handling for sequence builder, ensuring more robust operations.
  • Added functionality to manage removal of previous owners in space updates.
  • Introduced a new utility function for calculating differences between lists.

• Refactor

  • Renamed sequences and collections variables for better consistency and readability.
  • Adjusted SpacesKeeper methods to support additional parameters for more efficient updates.

[coderabbitai[bot]]

Walkthrough

## Walkthrough The key changes involved renaming variables for sequence and collection handling to follow a consistent naming convention across the `warden/x/warden/keeper` package. This included modifications to the declarations of exported entities and error handling improvements. Additionally, changes in the `SpacesKeeper` struct and methods now more effectively handle updates by considering the previous state of space owners. ## Changes | Files | Change Summary | |----------------------------------------|------------------------------------------------------------------------------------------------------------------| | `warden/x/warden/keeper/keeper.go` | Renamed sequence and collection variables for keychains, key requests, and sign requests. Added error handling. | | `warden/x/warden/keeper/spaces.go` | Updated naming conventions for sequence. Enhanced `SpacesKeeper` to handle previous space owners during updates. Added a new helper function `subtract`. | ## Sequence Diagram(s) Below is a sequence diagram for the updated `SpacesKeeper`'s `Set` method and `updateSpaceOwners` function. ```mermaid sequenceDiagram participant Client participant SpacesKeeper participant Collections as collections.SchemaBuilder participant Repo Client->>SpacesKeeper: Set(ctx, space) SpacesKeeper->>Collections: Retrieve OldSpace Collections-->>SpacesKeeper: OldSpace SpacesKeeper->>SpacesKeeper: extract OldOwners SpacesKeeper->>SpacesKeeper: updateSpaceOwners(ctx, space, OldOwners) SpacesKeeper->>Collections: Update Space Owners Collections-->>SpacesKeeper: Confirmation SpacesKeeper-->>Client: Set Confirmation Client->>SpacesKeeper: updateSpaceOwners(ctx, space, oldOwners) activate SpacesKeeper SpacesKeeper->>Repo: Remove Old Owners Repo-->>SpacesKeeper: Confirmation SpacesKeeper->>Repo: Add New Owners Repo-->>SpacesKeeper: Confirmation deactivate SpacesKeeper SpacesKeeper-->>Client: updateSpaceOwners Confirmation ```

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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 resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[github-actions[bot]]

Hey @Pitasi and thank you for opening this pull request! 👋🏼

It looks like you forgot to add a changelog entry for your changes. Make sure to add a changelog entry in the 'CHANGELOG.md' file.