Skip to content

Conversation

danenbm
Copy link
Contributor

@danenbm danenbm commented Jul 2, 2025

Notes

Prevents updating the authority for all of the assets in an mpl-core collection for every collection change.

Instead, we update all assets in the collection if:

  1. The collection is found and its authority has changed.
  2. The collection is not found.

Case 2 requires us to attempt to update all assets in a collection because assets can be indexed before the collection itself.

Testing

  • Created a collection and verified collection_authority_changed condition was triggered, since collection was not yet indexed.
  • Created an asset in the collection and verified collection_authority_changed condition was NOT triggered for either the collection or asset.
  • Updated the collection's update authority and verified collection_authority_changed condition was triggered and both the collection's authority and asset's authority was updated.
  • Updated the collection's name and verified collection_authority_changed was NOT triggered.

Copy link

coderabbitai bot commented Jul 2, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

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

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

@danenbm danenbm marked this pull request as ready for review July 2, 2025 07:17
@danenbm danenbm force-pushed the danenbm/add-leaf-schema-version branch from 8c9c023 to f9784d2 Compare July 2, 2025 23:42
@danenbm danenbm force-pushed the danenbm/limit-auth-update branch from f4e639a to de7acc7 Compare July 2, 2025 23:52
blockiosaurus
blockiosaurus previously approved these changes Jul 3, 2025
Comment on lines +108 to +128
// If found, determine whether the authority has changed.
let collection_authority_changed = match account_data {
MplCoreAccountData::Collection(_) => {
let existing_record = asset_authority::Entity::find()
.filter(asset_authority::Column::AssetId.eq(id_vec.clone()))
.one(conn)
.await
.map_err(|db_err| ProgramTransformerError::AssetIndexError(db_err.to_string()))?;

// We need to update all assets in the collection if:
// 1. The collection is found and its authority has changed.
// 2. The collection is not found.
//
// Case 2 requires us to attempt to update all assets in a collection because assets
// can be indexed before the collection itself.
existing_record
.map(|record| record.authority != update_authority)
.unwrap_or(true)
}
_ => false,
};
Copy link
Collaborator

@kespinola kespinola Jul 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really want to avoid doing lookups while indexing. Is there a way to do this where you join in record you want to check against and then adjusting the where class of the insert or update?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i will look into this

Base automatically changed from danenbm/add-leaf-schema-version to main July 11, 2025 23:19
@danenbm danenbm dismissed blockiosaurus’s stale review July 11, 2025 23:19

The base branch was changed.

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.

3 participants