-
Notifications
You must be signed in to change notification settings - Fork 212
[$60] Rating on default profile does not match the rating on the rating history graph #4794
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
Comments
@rootelement API returning different rating in |
Why are the latest ratings' history values have lower values? |
@luizrrodrigues @Oanh-and-only-Oanh Also check this on March 17, 2020 at around 12:17:32 PHT, I won an F2F and my rank color is still YELLOW |
@Oanh-and-only-Oanh @luizrrodrigues The V5 maximumRating: 1669, it should be maximumRating: 1941 |
@urwithat Can you help in this one? |
@cagdas001 - v3 member stats should be working fine but seems the v5 stats need a fix. Figuring out the root cause will take a couple of days. |
@urwithat if you're talking about the issue #4947 we're getting the rating from resources-api there. The issue is that resources-api returns the maxRating instead of particular rating for the track. Neither frontend nor the resources-api calls member-api. resources-api directly gets/queries Member Stats from DB. You can take a look at this comment: #4947 (comment)
By the way, for the V5 stats endpoint, I realized yesterday when I was working on the #4947, it actuslly returns all ratings along with maxRating so you can access particular ratings as well. Just take a look at the response structure, all ratings are there |
Contest https://www.topcoder.com/challenges/30142851 has been created for this ticket. |
Contest https://www.topcoder.com/challenges/30142851 has been updated - it has been assigned to cagdas001. |
@cagdas001, so is this a resource api issue and that it should return the maxRating instead of particular rating for the track? |
What I wrote applies to #4947 This issue is another story I guess, have not investigated this one. In #4947 , you're right we're getting rating from resources-api so it's a resources-api issue. Take a look at this comment #4947 (comment) for detailed info |
Describe the bug
Rating on default profile does not match the rating on the rating history graph
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The rating on the default profile page should match the current rating the rating history graph.
Actual behavior
The ratings on the default profile page is different than the current rating on the history graph.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: