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

Populate memo in blockstore signatures-for-address (backport #19515) #19604

Merged
merged 1 commit into from
Sep 3, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 3, 2021

This is an automatic backport of pull request #19515 done by Mergify.
Cherry-pick of 5fa3e57 has failed:

On branch mergify/bp/v1.6/pr-19515
Your branch is up to date with 'origin/v1.6'.

You are currently cherry-picking commit 5fa3e5744.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   ledger/src/blockstore_db.rs

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   core/src/transaction_status_service.rs
	both modified:   ledger/src/blockstore.rs
	deleted by us:   transaction-status/src/extract_memos.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


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.io/

@mergify mergify bot added conflicts automerge Merge this Pull Request automatically once CI passes labels Sep 3, 2021
@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from d60d712 to ae66bb7 Compare September 3, 2021 16:01
@solana-grimes solana-grimes removed the automerge Merge this Pull Request automatically once CI passes label Sep 3, 2021
@solana-grimes
Copy link
Contributor

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

@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from ae66bb7 to 8082511 Compare September 3, 2021 16:04
@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Sep 3, 2021
@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2021

automerge label removed due to a CI failure

@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from 8082511 to 4b38466 Compare September 3, 2021 16:06
@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Sep 3, 2021
@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2021

automerge label removed due to a CI failure

@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from 4b38466 to 630bd4e Compare September 3, 2021 16:23
@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Sep 3, 2021
@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2021

automerge label removed due to a CI failure

@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from 630bd4e to 26ab9db Compare September 3, 2021 16:31
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Sep 3, 2021
@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2021

automerge label removed due to a CI failure

@mergify mergify bot removed the automerge Merge this Pull Request automatically once CI passes label Sep 3, 2021
* Add TransactionMemos column family

* Traitify extract_memos

* Write TransactionMemos in TransactionStatusService

* Populate memos from column

* Dedupe and add unit test

(cherry picked from commit 5fa3e57)
@CriesofCarrots CriesofCarrots force-pushed the mergify/bp/v1.6/pr-19515 branch from 26ab9db to d777415 Compare September 3, 2021 16:40
@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Sep 3, 2021
@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2021

automerge label removed due to a CI failure

@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Sep 3, 2021
@codecov
Copy link

codecov bot commented Sep 3, 2021

Codecov Report

Merging #19604 (d777415) into v1.6 (db65b4e) will increase coverage by 0.0%.
The diff coverage is 76.8%.

@@           Coverage Diff            @@
##             v1.6   #19604    +/-   ##
========================================
  Coverage    82.3%    82.3%            
========================================
  Files         424      424            
  Lines      118641   118708    +67     
========================================
+ Hits        97645    97759   +114     
+ Misses      20996    20949    -47     

@mergify mergify bot merged commit b4fdce9 into v1.6 Sep 3, 2021
@mergify mergify bot deleted the mergify/bp/v1.6/pr-19515 branch September 3, 2021 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this Pull Request automatically once CI passes conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants