Skip to content

remove chainId#1338

Merged
alexcos20 merged 1 commit intomainfrom
bug/remove_chainId_from_persistent
Apr 20, 2026
Merged

remove chainId#1338
alexcos20 merged 1 commit intomainfrom
bug/remove_chainId_from_persistent

Conversation

@alexcos20
Copy link
Copy Markdown
Member

Remove chainId from persistentStorage commands, as it was not needed

@alexcos20
Copy link
Copy Markdown
Member Author

/run-security-scan

Copy link
Copy Markdown
Member Author

@alexcos20 alexcos20 left a comment

Choose a reason for hiding this comment

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

AI automated code review (Gemini 3).

Overall risk: low

Summary:
This pull request consistently removes the chainId parameter from PersistentStorageGetBucketsCommand and PersistentStorageDeleteFileCommand across the command interfaces, their respective handlers, and HTTP route parsing logic. The change simplifies the API by eliminating a parameter that is presumed to be unnecessary or incorrectly applied to persistent storage operations. The branch name bug/remove_chainId_from_persistent suggests this is a corrective measure to fix an underlying issue or improve clarity.

Comments:
• [INFO][style] It looks like the JSDoc comment /** Ethereum address; only buckets with this stored owner are returned (then filtered by ACL). */ for the owner field was removed along with chainId. This comment seems to describe the owner field's purpose and might still be relevant if owner's functionality hasn't changed. Could you please confirm if this comment was intentionally removed or if it was an accidental deletion during the chainId removal?

@alexcos20 alexcos20 merged commit 13fca26 into main Apr 20, 2026
25 of 27 checks passed
@alexcos20 alexcos20 deleted the bug/remove_chainId_from_persistent branch April 20, 2026 11:22
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.

2 participants