1878353 - app.qonto.com doesn't load correctly

Status: RESOLVED FIXED

(Core :: JavaScript Engine: JIT, defect)

Description

[Ksenia Berezina [:ksenia]]

We've received a report in https://github.com/webcompat/web-bugs/issues/132940 where the sites fails to load with an error:
Error while processing route: protected.index can't convert symbol to number

The error appears to be happening in this function (in the for (const r in e) t[${ i }.${ r }] = e[r] loop):

            K = Object.prototype.hasOwnProperty;
            function W(e) {
              const t = new G;
              for (const i in e) {
                if (!K.call(e, i)) continue;
                const r = e[i];
                if ('object' == typeof r && r) {
                  const e = W(r);
                  for (const r in e) t[`${ i }.${ r }`] = e[r]
                } else t[i] = r
              }
              return t
            }

(though when I try to log the values inside the object t, it doesn't error out anymore :/)

From mozregression:

25:43.58 INFO: No more integration revisions, bisection finished.
25:43.58 INFO: Last good revision: 888623deeb3d6817ff7aece0e8898f9624873dac
25:43.58 INFO: First bad revision: 7ad5c59c746bbde34ba4a1bb08ba6aa1c65dbacd
25:43.58 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=888623deeb3d6817ff7aece0e8898f9624873dac&tochange=7ad5c59c746bbde34ba4a1bb08ba6aa1c65dbacd

Comment 1

[Ksenia Berezina [:ksenia]]

Hi Nicolas, could you please take a look at this?

Comment 2

[Dennis Schubert [:denschub]]

[Tracking Requested - why for this release]:

Relatively popular site (rank ~1k in France, ~18k globally), and no obvious way for us to ship an intervention for this.

Comment 3

[Nicolas B. Pierron [:nbp]]

(In reply to Ksenia Berezina [:ksenia] from comment #1)

Hi Nicolas, could you please take a look at this?

I looked into it, and apparently this is a new failure that we had not discovered yet.
To avoid adding another week of latency, we decided to backout the bad changes.

This should solve this problem in the following releases of Nightly.
The backout is being tracked by Bug 1876978.

Comment 4

[Dominik Bay [:eimann]]

Confirmed, 20240203092120 is working with the website again. Thanks for fixing this!