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

gui(installer): use fixed keys ordering #1442

Merged

Conversation

jp1ac4
Copy link
Collaborator

@jp1ac4 jp1ac4 commented Nov 6, 2024

This is to fix #1439. It follows the same approach as used in the settings to ensure consistent ordering when iterating over keys.

This follows the same approach as used in the settings.
@edouardparis
Copy link
Member

edouardparis commented Nov 6, 2024

I think it would be cleaner to change the keys alias map in Context struct for a BTreeMap for which iterators always respect an order. Thresh_origins result map is the culprit

Copy link
Member

@edouardparis edouardparis left a comment

Choose a reason for hiding this comment

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

utACK 86cebc2

@edouardparis edouardparis merged commit ff968ea into wizardsardine:master Nov 6, 2024
31 checks passed
edouardparis added a commit that referenced this pull request Nov 6, 2024
…rdering

82ef34e gui(installer): use fixed keys ordering (Michael Mallan)

Pull request description:

  Backport of #1442.

ACKs for top commit:
  edouardparis:
    utACK 82ef34e

Tree-SHA512: 4445cf37608a8d9f42512d25d3b54129e8d8d525fe73912f9cf23a18722d9deb5545304c80558f6afc202e7e04ef2a3d98caf6e1111f17aa958ef8aca1125d98
@jp1ac4 jp1ac4 deleted the gui-use-fixed-keys-ordering branch November 6, 2024 15:14
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.

Aliases order in the wallet policy descriptor changes according to check on descriptor registration
2 participants