Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Issues with Next Forging Turn (/api/delegates/forgers) #3304

Closed
simonmorgenthaler opened this issue Apr 11, 2019 · 2 comments
Closed

Issues with Next Forging Turn (/api/delegates/forgers) #3304

simonmorgenthaler opened this issue Apr 11, 2019 · 2 comments
Assignees

Comments

@simonmorgenthaler
Copy link

Expected behavior

The api call /delegates/forgers should return always the correct order (ordered by 'nextSlot') of the current delegates list, to get a consistent value when a delegate will forge its next block

Actual behavior

The api call /delegates/forgers returns inconsistent values. It is not ordered by 'nextSlot'. Well, sometimes it seems to be ordered correctly, but not always.

Steps to reproduce

call /delegates/forgers multiple times and compare the returned list

Which version(s) does this affect? (Environment, OS, etc...)

1.6.0-rc.3

@ManuGowda
Copy link
Contributor

@michielmulders please ensure you add the rite tests covering the issue raised, currently we do not have any tests to identify the issues raised, thanks.

@michielmulders
Copy link
Contributor

@simonmorgenthaler Thanks a lot for reporting the bug. The custom sort function was indeed not behaving as expected. PR with tests covering this behavior will be created later today. Happy days! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants