Ratings number not updating on member profile

[Oanh-and-only-Oanh]

Issue: the rating number for Code is not updating after a dev challenge even though the graph updated.

Expected behavior: the rating number should update appropriately after dev challenges as well as the cooresponding graph

To reproduce

1. Go to: https://www.topcoder.com/members/birdofpreyru/details/?track=DEVELOP&subTrack=CODE
2. see rating in yellow read 1664 but graph reads 1809
3. rating number and graph do not match

[adroc-tc]

@Oanh-and-only-Oanh checking in on this issue - is there a date to tackle this issue?

[Oanh-and-only-Oanh]

@adroc-tc, we'll try to tackle this next week.

[skyhit]

@Oanh-and-only-Oanh , the main reason is the data is retrieved from different backend apis.

1. 1664 is from api call https://api.topcoder.com/v3/members/birdofpreyru/stats
2. while 1809 is getting from https://api.topcoder.com/v3/members/birdofpreyru/stats/history

so here are two solutions.

1. update the UI to use just the last rating of last challenge from Integrate with accounts-app for authentication #2.
2. we need to research into the v3 member apis.

which do you prefer?

[Oanh-and-only-Oanh]

@skyhit,

Please go with solution #1. "update the UI to use just the last rating of last challenge from #2."

[harshitmehta15]

Hey @Oanh-and-only-Oanh @skyhit there is a bigger issue here, I think the loader is not updating stats in Dynamo properly.

Take a look at tourist

So tourist's rating should be - from (history)
{"challengeId":17900,"challengeName":"SRM 782","date":"2020-03-28T00:00:00.000Z","rating":3751.0,"placement":1,"percentile":99.9552

Howver in stats
DATA_SCIENCE":{"challenges":603,"wins":35,"mostRecentEventName":"SRM 774","mostRecentEventDate":"2020-01-11T00:00:00.000Z","mostRecentSubmission":"2019-12-11T13:00:12.921Z"

SRM 774 to SRM 782 the stats are not getting updated correctly.

Please check the loaders.
cc: @adroc-tc

[Oanh-and-only-Oanh]

@SathyaJayabal, can you check to see if this is still an issue in PROD?

[SathyaJayabal]

@Oanh-and-only-Oanh , this issue is fixed on production