Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrations are not migrating payloads in PathCapabilityStorageDomain #6069

Closed
fxamacker opened this issue Jun 11, 2024 · 0 comments · Fixed by #6070
Closed

Migrations are not migrating payloads in PathCapabilityStorageDomain #6069

fxamacker opened this issue Jun 11, 2024 · 0 comments · Fixed by #6070
Assignees
@fxamacker
Labels
Bug Something isn't working

Comments

@fxamacker
Copy link
Member

Currently, payloads in path capability storage domain are not getting migrated. This is caused by migrations missing PathCapabilityStorageDomain during traversal and storage health check.

This affects atree migration and maybe also Cadence 1.0 migration.

I found this bug while investigating why number of payloads differ when porting some Cadence 1.0 migration optimizations to atree migration in flow-go PRs #6043 #6046 #6047 #6048 #6049 #6050.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fxamacker fxamacker

Labels
Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix Cadence 1.0 migration missing PathCapabilityStorageDomain onflow/flow-go
1 participant
@fxamacker