Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

removes next_shred_index from return value of entries to shreds api (backport #21961)#21980

Merged
mergify[bot] merged 1 commit intov1.9from
mergify/bp/v1.9/pr-21961
Dec 17, 2021
Merged

removes next_shred_index from return value of entries to shreds api (backport #21961)#21980
mergify[bot] merged 1 commit intov1.9from
mergify/bp/v1.9/pr-21961

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Dec 17, 2021

This is an automatic backport of pull request #21961 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@mergify mergify Bot added the automerge Merge this Pull Request automatically once CI passes label Dec 17, 2021
@behzadnouri
Copy link
Copy Markdown
Contributor

@Mergifyio refresh

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Dec 17, 2021

refresh

✅ Pull request refreshed

…21961)

next-shred-index is already readily available from returned data shreds.
The commit simplifies the api for upcoming changes to erasure coding
schema which will require explicit tracking of indices for coding shreds
as well as data shreds.

(cherry picked from commit 89d66c3)
@behzadnouri behzadnouri force-pushed the mergify/bp/v1.9/pr-21961 branch from adc5eee to 53ef18e Compare December 17, 2021 15:42
@solana-grimes
Copy link
Copy Markdown
Contributor

😱 New commits were pushed while the automerge label was present.

@solana-grimes solana-grimes removed the automerge Merge this Pull Request automatically once CI passes label Dec 17, 2021
@mergify mergify Bot added the automerge Merge this Pull Request automatically once CI passes label Dec 17, 2021
@mergify mergify Bot merged commit e572678 into v1.9 Dec 17, 2021
@codecov
Copy link
Copy Markdown

codecov Bot commented Dec 17, 2021

Codecov Report

Merging #21980 (53ef18e) into v1.9 (f452100) will increase coverage by 0.0%.
The diff coverage is 65.5%.

@@           Coverage Diff           @@
##             v1.9   #21980   +/-   ##
=======================================
  Coverage    81.2%    81.2%           
=======================================
  Files         515      515           
  Lines      143751   143750    -1     
=======================================
+ Hits       116818   116842   +24     
+ Misses      26933    26908   -25     

@mergify mergify Bot deleted the mergify/bp/v1.9/pr-21961 branch December 17, 2021 17:58
@brooksprumo brooksprumo mentioned this pull request Jan 5, 2022
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 4, 2022

This PR has been automatically locked since there has not been any activity in past 14 days after it was merged.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

automerge Merge this Pull Request automatically once CI passes locked PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants