Errors in console are unwieldy #16266

adamreisnz · 2017-10-11T11:56:20Z

I'm submitting a ...

bug report
feature request
other (Please do not submit support requests here (see above))

Current behavior:
Ok, brace yourselves 😆

For full effect to illustrate my pain point about this issue, I'm going to copy past the full error that presents itself in my console log. I'm not going to wrap it in code quotes, because then the lines don't wrap and you don't experience the full problem.

Please scroll past it to read the rest of the issue.

Expected / new behavior:
Now that you've scrolled down and reached this point, try to actually identify what the error was. You have to scroll all the way back up to the top, because the actual useful error information is at the top of this blob of useless data.

Expected behaviour is to see an error like this, which contains all the info you need:

Uncaught Error: [$injector:modulerr] Failed to instantiate module App due to:
Error: [$injector:modulerr] Failed to instantiate module App.Account due to:
Error: [$injector:modulerr] Failed to instantiate module App.Account.Pay due to:
Error: [$injector:modulerr] Failed to instantiate module App.Account.Pay.Summary.Card due to:
Error: [$injector:nomod] Module 'App.Account.Pay.Summary.Card' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.6.6/$injector/nomod?p0=App.Account.Pay.Summary.Card
    at http://localhost:8080/lib/angular.js:51:12
    at http://localhost:8080/lib/angular.js:1140:17
    at ensure (http://localhost:8080/lib/angular.js:1114:38)
    at module (http://localhost:8080/lib/angular.js:1138:14)
    at http://localhost:8080/lib/angular.js:2612:22
    at forEach (http://localhost:8080/lib/angular.js:133:20)
    at loadModules (http://localhost:8080/lib/angular.js:2596:5)
    at http://localhost:8080/lib/angular.js:2614:40
    at forEach (http://localhost:8080/lib/angular.js:133:20)
    at loadModules (http://localhost:8080/lib/angular.js:2596:5)

I don't even know how to interpret the rest of the error or what to do with such an excessive stack trace full of url encoded data.

Minimal reproduction of the problem with instructions:
Just trigger any angular error.

AngularJS version: 1.6.6

Browser:
All afaik

Suggestions for fix:
There are several options to alleviate this problem imo, ranging from my most preferred to least preferred (but any solution is better than having to scroll up 200 pages just to see what Angular wants from me).

Get rid of the excessive information and just display the last error with the corresponding stack.
Introduce a config setting where we can control whether we want the full load of error data, or just the short version as mentioned under 1.
Append the actual legible/informative error message at the bottom of all this error junk so that at least we don't have to scroll up to see the message.

It appears the bulk of junk comes from Angular trying to create a link to the error page with more information, but it's beyond me why it would require so much data.

The text was updated successfully, but these errors were encountered:

Narretz · 2017-10-11T12:11:21Z

Hi @adamreisnz this is a known issue, see e.g. here: #14744

The error is so long because we include the stack in the url so that we can show it in the error page. Since the url must be encoded, it can get very long.

There's a PR to restrict the length of the error url that needs fixing up here: #15707

You can get involved with this, as it is currently stale. :<

adamreisnz · 2017-10-11T19:09:47Z

@Narretz thanks I'll subscribe there.

Narretz closed this as completed Oct 11, 2017

Narretz added the resolution: duplicate label Oct 11, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Errors in console are unwieldy #16266

Errors in console are unwieldy #16266

adamreisnz commented Oct 11, 2017 •

edited

Loading

Narretz commented Oct 11, 2017

adamreisnz commented Oct 11, 2017

Errors in console are unwieldy #16266

Errors in console are unwieldy #16266

Comments

adamreisnz commented Oct 11, 2017 • edited Loading

Narretz commented Oct 11, 2017

adamreisnz commented Oct 11, 2017

adamreisnz commented Oct 11, 2017 •

edited

Loading