Challenge phases are out of sync between V4 and V5

[SathyaJayabal]

We can see many challenges that are closed still in the active challenges. Also many of the Ongoing challenges in Open for registration. On looking at the api responses we can see that the api responses for V4 and V5 have different data.

Examples:
https://www.topcoder.com/challenges/30128012 - Closed
https://beta-community-app.topcoder.com/challenges/7f9b4dfc-14b8-463d-9651-c06cbb842d6d - Ongoing

https://www.topcoder.com/challenges/30130268 - Ongoing
https://beta-community-app.topcoder.com/challenges/2197c7a8-525c-4b67-829b-b4981ff15674 - Open for Registration(Stalled)

cc @lakshmiathreya @rootelement @sushilshinde

[SathyaJayabal]

topcoder-platform/challenge-api#186

[rootelement]

@SathyaJayabal @lakshmiathreya Can you guys install this browser extension so when you show API output, it's clearer to read?

https://chrome.google.com/webstore/detail/json-formatter/bcjindcccaagfpapjjmafapmmgkkhgoa?hl=en

Also, if you're showing comparisons like this, it helps me if you not only provide the links, but pull out the v5:updated, v4:updatedAt properties for comparison. I'm going to continue reviewing this. Thanks!

[rootelement]

I'm sorry, nevermind about the updated property. i forgot that's not provided by v4

[rootelement]

Please review. The example here lines up now:
http://api.topcoder.com/v4/challenges/30128012
http://api.topcoder.com/v5/challenges?legacyId=30128012
@SathyaJayabal ^

[rootelement]

Is this still an issue? After the recent sync update and fixes to the legacy processors, this seems to be fine.

[mtwomey]

Yes kindly reconfirm this one due to recent updates.

[SathyaJayabal]

Still an issue @rootelement @mtwomey
topcoder-platform/challenge-api#186 (comment)

[lakshmiathreya]

Pls note that the discrepancies across V4 (Prod) & V5 (Beta) are largely due to pending Data migration issues which are work in progress currently: https://github.com/topcoder-platform/challenge-api/issues?q=is%3Aissue+is%3Aopen+label%3AP0

[Oanh-and-only-Oanh]

closing because this is a duplicate issue