This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
(CRO-677) Problem: The result of the list address API is not ordered by creation order #777
Assignees
Comments
yihuang
added a commit
to yihuang/chain
that referenced
this issue
Jan 20, 2020
… stable Solution: - change `staking_keys`/`root_hashes` from `BTreeSet` to `Vec`
yihuang
added a commit
to yihuang/chain
that referenced
this issue
Jan 20, 2020
… stable Solution: - change `staking_keys`/`root_hashes` from `BTreeSet` to `Vec`
|
The title should be: The result of the list address API is not ordered by creation order. When a new address added, the whole list gets re-ordered. |
bors bot
added a commit
that referenced
this issue
Jan 20, 2020
928: Problem (Fix #777): Order of client list address api is not sorted by creation order. r=tomtau a=yihuang Solution: - change `BTreeSet` to `IndexSet` This is required by new integration tests, also more intuitive to user. Co-authored-by: yihuang <[email protected]>
tomtau
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The address list returned by the client should be ordered stable, e.g. by creation order.
Python integration tests use address list API to get the bonded/unbonded stacking address, it’s not stable with current API.
The text was updated successfully, but these errors were encountered: