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

fix: Improve quorum data caching and cleanup #5731

Merged
merged 10 commits into from
Nov 29, 2023

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Nov 25, 2023

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@UdjinM6 UdjinM6 added this to the 20.1 milestone Nov 25, 2023
@UdjinM6 UdjinM6 changed the title Fix quorum data cleanup fix: Fix quorum data caching and cleanup Nov 25, 2023
@UdjinM6 UdjinM6 changed the title fix: Fix quorum data caching and cleanup fix: Improve quorum data caching and cleanup Nov 26, 2023
@UdjinM6 UdjinM6 force-pushed the fix_quorum_data_cleanup branch from 27dadec to 0b801c6 Compare November 26, 2023 01:41
@UdjinM6 UdjinM6 marked this pull request as ready for review November 26, 2023 13:43
@UdjinM6 UdjinM6 requested review from ogabrielides and PastaPastaPasta and removed request for ogabrielides November 26, 2023 13:43
Copy link
Collaborator

@ogabrielides ogabrielides left a comment

Choose a reason for hiding this comment

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

Looks good in general, some change though:

src/llmq/utils.cpp Outdated Show resolved Hide resolved
src/llmq/utils.cpp Outdated Show resolved Hide resolved
src/llmq/quorums.cpp Outdated Show resolved Hide resolved
@knst knst self-requested a review November 27, 2023 16:16
knst
knst previously approved these changes Nov 27, 2023
Copy link
Collaborator

@knst knst left a comment

Choose a reason for hiding this comment

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

LGTM

ogabrielides
ogabrielides previously approved these changes Nov 27, 2023
Copy link
Collaborator

@ogabrielides ogabrielides left a comment

Choose a reason for hiding this comment

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

ACK

src/llmq/quorums.cpp Outdated Show resolved Hide resolved
src/llmq/quorums.cpp Outdated Show resolved Hide resolved
PastaPastaPasta pushed a commit that referenced this pull request Nov 27, 2023
#5732)

## Issue being fixed or feature implemented
#4788 (comment)

noticed while working on #5731

## What was done?

## How Has This Been Tested?
run a node, check logs - there is a meaningful time span between `start`
and `done` now and not just zeros all the time.

## Breaking Changes

## Checklist:
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone _(for repository
code-owners and collaborators only)_
Co-authored-by: PastaPastaPasta <[email protected]>
Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

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

utACK for squash merge

Copy link
Collaborator

@ogabrielides ogabrielides left a comment

Choose a reason for hiding this comment

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

utACK

Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

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

utACK for squash merge

@knst
Copy link
Collaborator

knst commented Nov 29, 2023

ci/gitlab/gitlab.com — Pipeline failed on GitLab https://gitlab.com/dashpay/dash/-/jobs/5639464111

CI still failed after I restarted it

@ogabrielides
Copy link
Collaborator

ci/gitlab/gitlab.com — Pipeline failed on GitLab https://gitlab.com/dashpay/dash/-/jobs/5639464111

CI still failed after I restarted it

Now it succeeded.

@PastaPastaPasta PastaPastaPasta merged commit 00a076d into dashpay:develop Nov 29, 2023
4 of 8 checks passed
ogabrielides pushed a commit to ogabrielides/dash that referenced this pull request Dec 4, 2023
## Issue being fixed or feature implemented

## What was done?

## How Has This Been Tested?


## Breaking Changes


## Checklist:
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone _(for repository
code-owners and collaborators only)_

---------

Co-authored-by: PastaPastaPasta <[email protected]>
ogabrielides pushed a commit to ogabrielides/dash that referenced this pull request Dec 4, 2023
dashpay#5732)

## Issue being fixed or feature implemented
dashpay#4788 (comment)

noticed while working on dashpay#5731

## What was done?

## How Has This Been Tested?
run a node, check logs - there is a meaningful time span between `start`
and `done` now and not just zeros all the time.

## Breaking Changes

## Checklist:
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone _(for repository
code-owners and collaborators only)_
@UdjinM6 UdjinM6 modified the milestones: 20.1, 20.0.2 Dec 4, 2023
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.

4 participants