-
Notifications
You must be signed in to change notification settings - Fork 13
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
Snap is inserting corrupted metadata into sectors_meta #191
Comments
Source of the issue: 4445520 |
How do we plan to generate the unsealed CID for affected sectors? Is it same as SDR or do we have to run EncodeInto? |
magik6k
added a commit
that referenced
this issue
Sep 16, 2024
* Start unseal impl * Complete Generate Key * Decode SDR func * most of SDR unseal * Fix an unholy out-of-order decode issue * storiface: standardize .tmp somewhat * make gen * wip snap * What * snap unseal test * add logging * phi-only test * SNAP DECODE WOOOORKS!!! * cleanup logging * parallel snap decode * select rhos on the fly * snap decode SealCall * unseal scheduling * Plumb unseal to curio run * make: Always build blst * CLI for managing unseals * Unseal preference aware GC * Fix into handling in GenerateSDR * Oh no, snap is outputting corrupted metadata * Deal with #191 * make gen * get unseal fully working * scrub unsealed command * fix unseal check * unseal: Use correct CID in decode * gc: Don't mark sectors still in unseal pipeline for removal * unseal pipeline gc * make gen * fix snap decode readers * config: EnableScrubUnsealed->EnableCommP * harmony: Advanced max counters * make gen * address review * make gen * harmony: Put max counter Limiter behind an interface
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The title is bad news
Good news:
The text was updated successfully, but these errors were encountered: