[Dev Env] Dates Sync Issue for New Challenges

[lakshmiathreya]

-- Launch seems to go fine - Challenge remains in Active State.
-- However, Dates don't get Synced correctly.
-- Registration remains disabled due to this.

[lakshmiathreya]

This is a blocker for End to End testing in the Dev Environment.
cc @drasticdpk @coderhacker @vikasrohit

[ThomasKranitsas]

@lakshmiathreya can you please share the challenge ID?

[rootelement]

@ThomasKranitsas
https://challenges.topcoder-dev.com/challenges/8f1e5cb3-b625-4247-b835-9328d4b46d56

[ThomasKranitsas]

It seems like the code is trying to read the actualEndDate while this has been removed and it's only available after the end of the phase. If the actualEndDate is not defined, you should fall back to the scheduledEndDate. The fix is on the frontend and not the API

[lakshmiathreya]

@ThomasKranitsas - wondering how this works in Prod but not Dev?

[rootelement]

@lakshmiathreya because prod is not using the v5 autopilot/scheduler. It's because now phases are managed correctly using that v5. Direct/OR/Legacy Autopilot was populating dates that don't actually matter until the phase time passes.

[lakshmiathreya]

@rootelement what's the ETA for the fix - this is a blocker for Dev testing ...

[ThomasKranitsas]

@lakshmiathreya the fix is to be done on the frontend. There's nothing to be fixed on the API

[rootelement]

We might need to make an assoc issue on the Community App. I've sent this to @sushilshinde that'll be up to him. It's a pretty minimal update on the UI side.

[lakshmiathreya]

cc @SathyaJayabal for followup on FE ...