You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently seeing some program submitter dashboards (first noticed with PACA-CA) crashing. The cause is an edge case in the returned clinical error data for donors.
This is happening because there are donor error records that have the errors property that is an empty array, so errors[0] is undefined.
This page should be updated to handle empty arrays gracefully.
The root cause of the issue has to be traced back to the argo clinical api that is generating the error data with this unexpected form.
Steps To Reproduce
Reproducible in production only, due to edge case in PACA-CA submitted clinical data. Program Submitted dashboard for PACA-CA will crash after load during rendering of the DonorSummaryTable.
Expected behaviour
Page should load without crashing with data in this edge case.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently seeing some program submitter dashboards (first noticed with PACA-CA) crashing. The cause is an edge case in the returned clinical error data for donors.
The specific crash is traced to the line: https://github.com/icgc-argo/platform-ui/blob/develop/components/pages/submission-system/program-dashboard/DonorDataSummary/DonorSummaryTable.tsx#L484
This is happening because there are donor error records that have the
errors
property that is an empty array, soerrors[0]
is undefined.This page should be updated to handle empty arrays gracefully.
The root cause of the issue has to be traced back to the argo clinical api that is generating the error data with this unexpected form.
Steps To Reproduce
Reproducible in production only, due to edge case in PACA-CA submitted clinical data. Program Submitted dashboard for PACA-CA will crash after load during rendering of the DonorSummaryTable.
Expected behaviour
Page should load without crashing with data in this edge case.
The text was updated successfully, but these errors were encountered: