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

Detect tracer key in sigverify (backport #25579) #25645

Merged
merged 1 commit into from
Jun 1, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 30, 2022

This is an automatic backport of pull request #25579 done by Mergify.
Cherry-pick of 90a3315 has failed:

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

You are currently cherry-picking commit 90a3315b6.
  (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:   core/src/sigverify.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   perf/src/sigverify.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.com

@mergify mergify bot added the conflicts label May 30, 2022
@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 May 30, 2022
@mergify
Copy link
Contributor Author

mergify bot commented May 30, 2022

automerge label removed due to a CI failure

@carllin carllin force-pushed the mergify/bp/v1.10/pr-25579 branch from ede31bd to 18acf7c Compare May 31, 2022 00:28
@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 May 31, 2022
@mergify
Copy link
Contributor Author

mergify bot commented May 31, 2022

automerge label removed due to a CI failure

* Mark the tracer transaction

* simplify tracer check

(cherry picked from commit 90a3315)
@carllin carllin force-pushed the mergify/bp/v1.10/pr-25579 branch from 18acf7c to d7e1627 Compare May 31, 2022 05:38
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label May 31, 2022
@mergify
Copy link
Contributor Author

mergify bot commented May 31, 2022

automerge label removed due to a CI failure

@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 May 31, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Jun 1, 2022

automerge label removed due to a CI failure

@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Jun 1, 2022
@mergify mergify bot merged commit e9ef15a into v1.10 Jun 1, 2022
@mergify mergify bot deleted the mergify/bp/v1.10/pr-25579 branch June 1, 2022 04:01
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.

1 participant