Skip to content

Document Metadata API: MetaFile hash matching issue with serialization #1392

@jku

Description

@jku

So far I've been assuming we can build the client and use the Metadata API to

  • deserialize what we get from the remote repo, and then
  • serialize the data to disk once we know it's valid

The issue here is "meta" in timestamp (and I suppose snapshot) can contain file hashes. If we only store on local disk what has been deserialized and then serialized these hashes will fail to match when they are next read from disk (because white space etc).

Fixing this in the client is easy but I wonder if there's something that needs to be done in metadata API to make this more obvious or a harder mistake to make.

Metadata

Metadata

Assignees

Labels

1.0.0 blockersTo be addressed before 1.0.0 releasebacklogIssues to address with priority for current development goalsdocumentationDocumentation of the project as well as procedural documentation

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions