Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Voting: Wrong rank and double entries #400

Closed
punkr0ck opened this issue Jun 13, 2017 · 7 comments
Closed

Voting: Wrong rank and double entries #400

punkr0ck opened this issue Jun 13, 2017 · 7 comments
Labels

Comments

@punkr0ck
Copy link

punkr0ck commented Jun 13, 2017

v1.0.0-rc.3 on Testnet

After logging into my testnet account, clicking on voting, searching for punkrock, I get wrong rank and double entries.

Expected behaviour

grafik

Actual behaviour

I searched for punkrock and got this:
grafik

Steps to reproduce

Log into your testnet account, click voting, search for punkrock.

@alepop
Copy link
Contributor

alepop commented Jun 13, 2017

look like peer return wrong response. http://testnet.lisk.io:7000/api/delegates/search?offset=0&limit=100&q=punk

@slaweet
Copy link
Contributor

slaweet commented Jun 13, 2017

There's really something wrong in the API endpoint. Other search terms do the same - delegates twice and rank double, e.g.: http://testnet.lisk.io:7000/api/delegates/search?offset=0&limit=100&q=joel

@reyraa reyraa added bug and removed bug labels Jun 13, 2017
@Isabello
Copy link

this might be an issue with the caching implementation in 0.9.0

Can you try against mainnet?

@Isabello
Copy link

Confirmed this is a bug with lisk core not with lisk nano

@punkr0ck
Copy link
Author

punkr0ck commented Jun 13, 2017

On Mainnet I don't get any values for "rank", "approval" and "uptime". At least, there are no double entries.

grafik

@Isabello
Copy link

yes those endpoints were modified in the 0.9.0 release

@karmacoma karmacoma added the bug label Jun 13, 2017
@Isabello Isabello added this to Ready in Version 1.0.0 Jun 13, 2017
@slaweet slaweet moved this from Ready to Backlog in Version 1.0.0 Jun 14, 2017
@slaweet slaweet removed this from Backlog in Version 1.0.0 Jun 14, 2017
@Isabello
Copy link

Since this is an issue with core, not with nano, and its already fixed in core, i have labeled wont-fix

I will leave it open until 0.9.0 is released so that duplicates dont get logged.

Repository owner locked and limited conversation to collaborators Jun 15, 2017
@Isabello Isabello removed the bug label Jun 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants