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

Remove encoded blob if confirmed #41

Merged
merged 1 commit into from
Nov 17, 2023

Conversation

ian-shim
Copy link
Contributor

@ian-shim ian-shim commented Nov 16, 2023

Why are these changes needed?

For a retry mechanism, we encode a blob again at different reference block number if the blob is in the middle of being dispersed because we don't know the status of that blob yet.
Once we know the blob has been dispersed successfully, we should remove it from the encoded blob store, so that we don't disperse the same blob again.

Checks

  • I've made sure the lint is passing in this PR.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
  • Testing Strategy
    • Unit tests
    • Integration tests
    • This PR is not tested :(

@ian-shim ian-shim force-pushed the remove-confirmed-encoded-blob branch from 1abead7 to 02c1708 Compare November 16, 2023 05:18
@ian-shim ian-shim marked this pull request as ready for review November 16, 2023 05:31
@ian-shim ian-shim force-pushed the remove-confirmed-encoded-blob branch from 02c1708 to 6906cf7 Compare November 17, 2023 00:39
@ian-shim ian-shim merged commit 663bd68 into Layr-Labs:master Nov 17, 2023
3 of 4 checks passed
teddyknox pushed a commit that referenced this pull request Nov 29, 2023
Signed-off-by: Wellington Barbosa <[email protected]>
Co-authored-by: Wellington Barbosa <[email protected]>
Co-authored-by: gpsanant <[email protected]>
Co-authored-by: Robert <[email protected]>
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