Power down amount is showing as 0 in wallet

[ng-gist]

Expected behavior

Steem Power in wallet should show correct amount of steem that will power down on the next power down date.

Actual behavior

Wallet is showing power down amount as 0 for the next power down date.

Prerequisite

1. You will need a profile with active power down.
2. The profile needs to be in last week of power down.

How To Re-produce

Go to following url to see the issue: https://busy.org/@mightypanda/transfers

• Browser: Chrome Version 69.0.3497.100 (Official Build) (64-bit)
• Operating system: OSX 10.11.6
• Version: 2.5.6

[economicstudio]

Hi @mightypanda-x, although I'm not a busy member, I explain this, since I implemented this cool :) feature. Hope you liked it.

Anyway, this isn't a problem of busy, but a problem of an alternative API server that Busy's currently using.

I've tested with local dev server with Steemit official API server and it's working without any problem. If you're a dev, you can test this easily by following https://github.com/busyorg/busy/blob/develop/README.md

Busy is using a different API server (probably anyx) due to some problem with Steemit API server. While mostly compatible, alternative API sever returns incorrect values for certain fields from time to time, in this case powerdown info.

@Sekhmet Do you continue to use anyx or some alternative server? Can we switch back to api.steemit.com? It'd be great if there is an option for that. e.g., steempeak has an option for users to choose API server. Thanks.

[ng-gist]

If the api returns invalid value, then the system should handle that particular input.

[economicstudio]

again this is my personal opinion. in some sense it's already doing what you suggested, "the api returns invalid value, then the system should handle that particular input." It shows 0 when it returns 0. 0 is special value so that you can easily notice there's some problem. Any further treatment? Well based on my experience, Busy team is using most of their time on Busy3.0, so you can't expect much from them. That's why I actually fix and implemented some features that I really want.

@Sekhmet It might be good at least one server (either production or dev) use the official API server so that some advanced user can easily notice whether it's simply API server problem or not.