Dear cBioPortal Support Team,
I am writing to report a recurring front-end rendering error that crashes the web interface during subgroup analysis. This issue occurs consistently when combining clinical filters with genomic queries.
Here are the specific steps that trigger the error First, I select a dataset such as the Lung Adenocarcinoma or Cervical Squamous Cell Carcinoma TCGA PanCancer Atlas. Second, I apply a clinical data filter to isolate a specific subcohort, specifically patients receiving Cisplatin treatment. Third, I submit a genomic query for genes such as PLSCR1 or CITED2. Finally, when navigating between the Plots tab, the Overlap interface, or attempting to define custom groups for Kaplan-Meier survival curves, the page crashes entirely.
The system displays the following error log details "type" equals "ErrorBoundary" "log" equals "NotFoundError Failed to execute 'removeChild' on 'Node' The node to be removed is not a child of this node." The URL parameters indicate that the tab_index is set to tab_visualize.
“https://www.cbioportal.org/results?plots_horz_selection=%7B%7D&plots_vert_selection=%7B%7D&plots_coloring_selection=%7B%7D&tab_index=tab_visualize&Action=Submit&session_id=69a6da351e0070aa094ecccb;{"type":"ErrorBoundary","log":"NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.”}”
This DOM state conflict prevents me from completing the clinical translational analysis and evaluating the prognostic difference for my research grant proposal. I would greatly appreciate it if your engineering team could investigate this UI rendering issue.
Thank you for your time and assistance.
Best regards,
Yu-Chin Liu,
PhD Project Assistant Professor
Department of Medicine, Fu Jen Catholic University
Dear Yu-Chin Liu,
Thank you for reporting this and for sharing the detailed steps and error log.
This seems to be related to the issue I just reported here: https://github.com/cBioPortal/cbioportal/issues/12254
Please feel free to follow the ticket and add any additional observations or details as a comment there. You’ll need a GitHub account to comment.
Best regards,
Ruslan,
SE4BIO