Description of problem: "invalid array length" JS error in admin console, most page can't be loaded Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2020-03-09-200240 How reproducible: Always Steps to Reproduce: 1. cluster admin logins to admin console Actual results: 1. "invalid array length" error in js console, most pages can not be loaded RangeError: "invalid array length" a main-chunk-bde0e19d70604dd3473b.min.js:1 getResources main-chunk-bde0e19d70604dd3473b.min.js:1 backend.js:6:2315 Expected results: 1. console should be loaded without error Additional info:
*** Bug 1811947 has been marked as a duplicate of this bug. ***
Hi Sam, The issue no longer reproduces on 4.3.0-0.nightly-2020-03-15-112942, did we changed anything to make it work? I saw the attached PR #4706 is closed
*** Bug 1815068 has been marked as a duplicate of this bug. ***
Please note that a different incarnation of the same issue happened also on 4.4.0-rc.1 and rc.2 (https://bugzilla.redhat.com/show_bug.cgi?id=1815068). The nightly close to this RC build (4.4.0-0.nightly-2020-03-11-212258) worked well though. So the issue seems to be still appearing.
*** Bug 1815558 has been marked as a duplicate of this bug. ***
A few more examples from a duplicate bug: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.4/1297 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.4/1296 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.4/1295
*** Bug 1805118 has been marked as a duplicate of this bug. ***
We've been able to reproduce with this script. The key is deleting the .cache-loader directory between builds: #!/bin/bash set -euo pipefail cd frontend rm -rf public/dist for i in {1..100} do echo "#### Running build #$i..." rm -rf .cache-loader yarn run build > "build-$i.out" 2>&1 if grep -F -l __spreadArrays public/dist/*.min.js; then echo "Found unexpected __spreadArrays!" exit 1 fi done
We've discovered that this is happening because we have two tsconfig.json files, one top-level and one for the topology package. ts-loader was picking up the wrong tsconfig.json in some cases. The topology version did not have `downlevelIteration` set, and they have different `target` values in master as well. https://github.com/TypeStrong/ts-loader/issues/647
Adding `Dependent Products` value back
*** Bug 1812622 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409