Closed Bug 1874386 Opened 2 years ago Closed 2 years ago

"Send error report" in DevTools does not include sent data on Bugzilla actually

Categories

(DevTools :: Debugger, defect)

Firefox 121
defect

Tracking

(firefox124 fixed)

RESOLVED FIXED
124 Branch
Tracking Status
firefox124 --- fixed

People

(Reporter: 5i13ghzt462u, Assigned: jdescottes)

References

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

When reporting Bug 1874382 I got a button "Send crash report" (respectively "Fehlermeldung einreichen" in German). That gave me this long URL:

https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&component=Debugger&comment=Error%3A%20%0ATypeError%3A%20selectedFrame%20is%20undefined%0A%0AReact%20Component%20Stack%3A%20%0A%20%20%20%20in%20Connect(Scopes)%0A%20%20%20%20in%20div%0A%20%20%20%20in%20aside%0A%20%20%20%20in%20div%0A%20%20%20%20in%20Accordion%0A%20%20%20%20in%20div%0A%20%20%20%20in%20div%0A%20%20%20%20in%20div%0A%20%20%20%20in%20SecondaryPanes%0A%20%20%20%20in%20Connect(SecondaryPanes)%0A%20%20%20%20in%20div%0A%20%20%20%20in%20div%0A%20%20%20%20in%20SplitBox%0A%20%20%20%20in%20AppErrorBoundary%0A%20%20%20%20in%20div%0A%20%20%20%20in%20App%0A%20%20%20%20in%20Connect(App)%0A%20%20%20%20in%20Provider%0A%20%20%20%20in%20Provider%0A%0AStacktrace%3A%20%0AmapStateToProps%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Fcomponents%2FSecondaryPanes%2FScopes.js%3A301%3A53%0AmapToPropsProxy%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1776%3A92%0AhandleNewState%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1937%3A41%0AhandleSubsequentCalls%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1954%3A30%0ApureFinalPropsSelector%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1959%3A32%0ArunComponentSelector%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1233%3A39%0AcomponentWillReceiveProps%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1357%3A23%0AcallComponentWillReceiveProps%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A8303%3A14%0AupdateClassInstance%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A8482%3A36%0AupdateClassComponent%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A10599%3A20%0AbeginWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A11419%3A16%0AperformUnitOfWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A14702%3A12%0AworkLoop%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A14720%3A24%0ArenderRoot%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A14803%3A15%0AperformWorkOnRoot%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A15655%3A17%0AperformWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A15567%3A24%0AperformSyncWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A15541%3A14%0ArequestWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A15410%3A5%0AscheduleWork%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A15224%3A16%0AenqueueSetState%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-dom.js%3A8192%3A17%0AComponent.prototype.setState%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact.js%3A328%3A16%0AonStateChange%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1412%3A16%0Anotify%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1159%3A21%0AnotifyNestedSubs%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1198%3A20%0AonStateChange%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Freact-redux.js%3A1409%3A16%0Adispatch%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Fredux.js%3A265%3A7%0AwaitUntilService%2F%3C%2F%3C%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Factions%2Futils%2Fmiddleware%2Fwait-service.js%3A71%3A24%0ApromiseMiddleware%2F%3C%2F%3C%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Factions%2Futils%2Fmiddleware%2Fpromise.js%3A39%3A14%0Acontext%2F%3C%2F%3C%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Factions%2Futils%2Fmiddleware%2Fcontext.js%3A85%3A12%0Athunk%2F%3C%2F%3C%2F%3C%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Factions%2Futils%2Fmiddleware%2Fthunk.js%3A29%3A100%0Adispatch%40resource%3A%2F%2Fdevtools%2Fclient%2Fshared%2Fvendor%2Fredux.js%3A681%3A28%0AmapFrames%2F%3C%40resource%3A%2F%2Fdevtools%2Fclient%2Fdebugger%2Fsrc%2Factions%2Fpause%2FmapFrames.js%3A149%3A13%0A

Actual results:

I tried it being logged in in Bugzilla or not, in any case (after login if needed) it redirect me to:

https://bugzilla.mozilla.org/enter_bug.cgi?format=guided#h=dupes|DevTools|Debugger

So all this huge URL essentially does is selecting product and component for me (DevTools|Debugger).

Expected results:

However, if you look into the URL it has much more data in it. It is supposedly thought to insert way more stuff including Stacktrace etc.

I now had to copy that manually (and somehow in BugZilla it includes line breaks between each line, e.g. of the stacktrace, which makes it even more ugly.)

This cannot be how it was/is intended.

Also tried switching to the non-guided-form, does not work.

The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Debugger

The link seems to work for us at the moment, but maybe there is a regression/issue with regular (ie non-mozilla employee) bugzilla accounts. Will create one and check.

We should also work on a copy button for that UI so that you can fetch the stacktrace/details easily, already tracked with another bug.

Flags: needinfo?(jdescottes)

The bug for the copy button: Bug 1759691 - Introduce Copy button for crash reports

See Also: → 1759691

:ochameau checked, and confirms the issue occurs with a non-employee account. We need to reach out to see if this is an expected behavior, and if yes we need to change the error reporting component to either bypass this issue or provide another way of getting the error details.

Flags: needinfo?(jdescottes)
Status: UNCONFIRMED → NEW
Ever confirmed: true

David, glob, non-employee accounts can't use the long URLs we provide to file bugs easily on Bugzilla. Do you known if this is intended? Is there any way we can workaround that? We want to include the stacktrace for a DevTools error in the bug description and right now we do it via URL parameter, but maybe there's a better way.

If this is not possible we will just change the UX to provide a copy button.

Flags: needinfo?(glob)
Flags: needinfo?(dkl)

Users without EDITBUGS have a simpler bug entry experience by default - you can see it here: https://bugzilla.mozilla.org/enter_bug.cgi?format=guided

You'll need to add format=__default__ to your query string to force users into the more advanced bug creation form.

Flags: needinfo?(glob)
Flags: needinfo?(dkl)
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dd979b5d8142 [devtools] Force __default__ format for bugzilla link in AppErrorBoundary r=devtools-reviewers,ochameau
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 124 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: