-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
GIVpower is acting strange #4326
Comments
The problem was a wrong power boosting record from a user who never have had a positive givpower balance 0xa198b3e3028882122d6365a2290906074aad3431 I removed his boosting record and the state would be fine after the cronjob is executed again. |
@RamRamez staging issue must be fixed now. The issue was database name was changed from staging -> staging2 and the db cron job was not updated to point to that db. |
@aminlatifi the totalPower in projectPowerView is still zero for all projects on staging and givPower is not shown on UI. Maybe we should refresh all views manually? https://staging.giveth.io/project/a-delicious-help?tab=givpower |
It's fixed now. It need some time |
@aminlatifi totalPower is still zero for all projects. Also UI not showing the GIVPower. |
![]() |
Staging balance aggregator has issue in querying subgraph
@mhmdksh can you look at this? |
@mohammadranjbarz GIVPower not showing is on staging only |
It's fixed now. |
@aminlatifi Thanks, it's ok now |
The rank of this project changed to 19 https://giveth.io/project/diamante-luz-center-for-regenerative-living-0?tab=givpower |
We've had several user reports of GIVpower acting strange.
Some projects not changing rank at the beginning of a new round, when the estimate has show for several rounds that the project's rank would increase. Several projects have their estimated rank the same as many other projects.
Some projects or specific boosting have their amount shows as
NaN
@RamRamez Did some investigation and here are his findings:
We should investigate further, find out what's wrong with GIVpower and execute the required fixes to bring it back to normal.
cc: @laurenluz
The text was updated successfully, but these errors were encountered: