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.

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

fix: unique metadata is not properly typed as a Uint8Array #3166

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

dbcfd
Copy link
Contributor

@dbcfd dbcfd commented Feb 16, 2024

No description provided.

@dbcfd dbcfd requested review from ukstv, PaulLeCam and stbrody February 16, 2024 00:28
@dbcfd
Copy link
Contributor Author

dbcfd commented Feb 16, 2024

This test will fail without this change.

@dbcfd dbcfd merged commit 63c7afc into develop Feb 16, 2024
6 checks passed
@dbcfd dbcfd deleted the fix/unique-type branch February 16, 2024 18:16
@stbrody
Copy link
Contributor

stbrody commented Feb 20, 2024

@dbcfd I'm confused why this PR was opened when we already had another PR with this same change in flight? #3141

I'd still really like to understand how and why we are winding up with data that isn't in the format we are expecting. I'm worried that this approach is papering over the symptoms rather than addressing the real source of the bug - which is whatever is generating data that doesn't have unique typed properly in the first place.

@stbrody
Copy link
Contributor

stbrody commented Feb 20, 2024

This test will fail without this change.

is it possible then that the Ceramic rust client isn't constructing/serializing the unique field in the same way as the javascript client does? Seems like that would be a bug in the rust client then.

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