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: Abstain and Lock trees for votes are now always first and fixed some limits #1921

Conversation

QuantumExplorer
Copy link
Member

@QuantumExplorer QuantumExplorer commented Jul 2, 2024

Issue being fixed or feature implemented

Changed some queries to use generics.
Added additional tests.
Abstain and Lock trees for votes are now always first.

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 added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@QuantumExplorer QuantumExplorer changed the title fix: limits on some query fixes fix: Abstain and Lock trees for votes are now always first and fixed some limits Jul 2, 2024
@QuantumExplorer QuantumExplorer merged commit 5857b9e into feat/contestedDocumentResolutionWithMasternodeVoting Jul 2, 2024
3 of 4 checks passed
@QuantumExplorer QuantumExplorer deleted the fix/contestedDocumentResolutionFixes5 branch July 2, 2024 09:37
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.

2 participants