You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time being, when there is only ShareVersionZero share version, this is not a problem, but when new share versions are introduced it could happen that the padding is created with different share version then the preceding shares which could lead to inconsistency. Passing blob.ShareVersion to NamespacePaddingShare and using it in the NewBuilder constructor should prevent this from happening.
The text was updated successfully, but these errors were encountered:
Builder for building padding shares is created using
ShareVersionZero
share version. This happens within functionNamespacePaddingShare
that is called from Export function when building padding shares (WriteNamespacePaddingShares->NamespacePaddingShares->NamespacePaddingShare->NewBuilder).It can be seen that the non padding shares within
Export
function are created ((Write->NewBuilder(blobNamespace, blob.ShareVersion, true).Init())) with shares Builder that takesblob.ShareVersion
.At the time being, when there is only
ShareVersionZero
share version, this is not a problem, but when new share versions are introduced it could happen that the padding is created with different share version then the preceding shares which could lead to inconsistency. Passingblob.ShareVersion
toNamespacePaddingShare
and using it in theNewBuilder
constructor should prevent this from happening.The text was updated successfully, but these errors were encountered: