v1.0 - Refactored legacy-submission-processor

[bountyC0d3r]

• all refactored legacy submission processor, implemented using nodejs v10
• single processor handeling MM and Non-MM submissions

[lakshmiathreya]

-- Verified MM and non-MM submissions
-- Verified setting of Initial and Final scores for MM submissions
-- Verified non-DMZ url for submissions

[lakshmiathreya]

cc @sachin-maheshwari can you pls update the current status here for future record? cc @drasticdpk

[sachin-maheshwari]

@lakshmiathreya on OR we are seeing multiple submissions for development challenge.

[drasticdpk]

Verified.
Dev Challenge

https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30058763

MM Challenge

https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30058764

User : Jcori

cc @sachin-maheshwari

[drasticdpk]

@sachin-maheshwari
Execution report for all track
https://docs.google.com/spreadsheets/d/1snA3TU1iYjkRjIDYv0dTKI6P55l9K69J2LiaHq-WmlQ/edit?usp=sharing

[drasticdpk]

Prod Verification

Development

Data Science

Design

QA

[drasticdpk]

Note : We have revert back it from prod successfully.
Reference : topcoder-platform/legacy-sub-processor#36
cc @sachin-maheshwari @lakshmiathreya

[sachin-maheshwari]

Thanks @drasticdpk.
Just for our reference -
This new version have following issues, we need to fix and verify again before deploying on prod -

• Multiple submissions are displaying at OR for development/code challenges. As per system-design, development/code only last submission should be considered, previous submission should be marked as delete ("upload_status_id" =2, upload table, tcs_catalog) in the legacy (informix) DB.
• In this version, there is no support of S3 URL update, which is required by support team to fix the existing issue (DMZ url missing)(not sure, but as informed by support team root cause is - due to large size of submission)

I am not sure how many other issues this version have. I think, QA team need to first analyze the existing functionalities of current (older) version.

[sachin-maheshwari]

@lakshmiathreya I didn't get, why you added its QA passed on prod. It was deployed on 1 March 2021 with "shapeup-pure-v5-task", Its failed on prod due to some funcalities were not working as mentioned above and we reverted yesterday.
Also i think it's not P0 ? its should be P1 or P2 ? as basic functionality (syncing to legacy system) is working.

[lakshmiathreya]

@sachin-maheshwari point noted - this is P0 but will remain open since resolution was not a fix but was a revert ...