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
{{ message }}
This repository has been archived by the owner on Apr 11, 2019. It is now read-only.
Adding logging on all these p variables (whatever they are) shows this problem:
// "usual" p:{"chunks": [// ... lots of data ...],"deletions": 22,"additions": 7,"from": "media/libcubeb/0002-Always-upmix-mono-to-the-first-two-channels-if-enoug.patch","to": "media/libcubeb/0002-Always-upmix-mono-to-the-first-two-channels-if-enoug.patch"}// "defective" p that breaks the front-end:{"chunks": [],"deletions": 2,"additions": 2,"from": ""}
@armenzg should we simply skip ps that don't have a .to attribute?
The text was updated successfully, but these errors were encountered:
The coverage front-end is broken on this revision: https://firefox-code-coverage.herokuapp.com/#/changeset/04dd259d71db60341016eccf53ced43742319631
The error is
TypeError: p.to is undefined
. Webpack and Devtools are not getting along well, but a simplegit grep
in the sources seems to point to:firefox-code-coverage-frontend/src/utils/data.js
Line 130 in a5f48df
Adding logging on all these
p
variables (whatever they are) shows this problem:@armenzg should we simply skip
p
s that don't have a.to
attribute?The text was updated successfully, but these errors were encountered: