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

v1.17: Adds more info to panic message in AccountsHashVerifier (backport of #35353) #35358

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 28, 2024

This is an automatic backport of pull request #35353 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

@brooksprumo
Copy link
Contributor

Justification for backporting:

So far this issue has been difficult to debug, as it often depends on the state of the machine (and filesystem) when the panic occurs. Without this backport, then we are effectively saying that we are OK with v1.17 not aiding in debugging. And then likely we would not backport a fix either (because if we aren't willing to backport debug info, why would we suddenly be OK with a more invasive fix).

@brooksprumo
Copy link
Contributor

Review requests:

Copy link

codecov bot commented Feb 28, 2024

Codecov Report

Attention: Patch coverage is 0% with 15 lines in your changes are missing coverage. Please review.

Project coverage is 81.6%. Comparing base (17eb75a) to head (ea41781).
Report is 4 commits behind head on v1.17.

Additional details and impacted files
@@            Coverage Diff            @@
##            v1.17   #35358     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%     
=========================================
  Files         806      806             
  Lines      218996   219092     +96     
=========================================
+ Hits       178758   178831     +73     
- Misses      40238    40261     +23     

Copy link
Contributor

@steviez steviez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm good with the BP; very narrow scope and will provide additional insight to debug a panic that we're seeing intermittently

Copy link
Contributor

@jeffwashington jeffwashington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@willhickey willhickey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved for stable branch

@brooksprumo
Copy link
Contributor

@sakridge Can I get your review on this backport?

@brooksprumo brooksprumo merged commit 1390ec9 into v1.17 Mar 1, 2024
33 checks passed
@brooksprumo brooksprumo deleted the mergify/bp/v1.17/pr-35353 branch March 1, 2024 21:32
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.

None yet

5 participants