Closed Bug 1607148 Opened 4 years ago Closed 4 years ago

Reps bundle was reverted to a previous version (but original files were not)

Categories

(DevTools :: Shared Components, defect, P3)

defect

Tracking

(firefox-esr68 unaffected, firefox73 wontfix, firefox74 wontfix, firefox75 fixed)

RESOLVED FIXED
Firefox 75
Tracking Status
firefox-esr68 --- unaffected
firefox73 --- wontfix
firefox74 --- wontfix
firefox75 --- fixed

People

(Reporter: nchevobbe, Assigned: nchevobbe)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

In Bug 1602804 the reps bundle file was directly modified, without modifying the original file.
It means that when doing a node bin/bundle.js now, the reps file will be updated to reflect what's in the original file.

Jaril, was the change intentional? It reverted a change that was made for performance reason, so I'm not sure

Flags: needinfo?(jarilvalenciano)

Jason, you reviewed that patch, could you tell me more about what it was for?

Flags: needinfo?(jlaster)

Yes, the change was intentional. We no longer need to release the object actors .

Watchpoints are now managed in a Map and not on Object actors, which makes a big difference for quality.

Flags: needinfo?(jlaster)
Flags: needinfo?(jarilvalenciano)

okay thanks for the answer

removed part of devtools-reps/src/object-inspector/actions.js as suggested in the patch D61086

Assignee: nobody → obdelnik
Status: NEW → ASSIGNED
Pushed by nchevobbe@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/17263a32d12e
Reps bundle was reverted to a previous version (but original files were not) r=nchevobbe

jest test failing, asked Stepan if he can look what's going on

Flags: needinfo?(nchevobbe)

(In reply to Jason Laster [:jlast] from comment #2)

Yes, the change was intentional. We no longer need to release the object actors .
Watchpoints are now managed in a Map and not on Object actors, which makes a big difference for quality.

Looking at the patch again and it looks weird to me.
We should still want to reach devtools/client/debugger/src/client/firefox/commands.js#90-99 for elements that are displayed in the ObjectInspector right (like the scopes panel, preview, watch expression, ...)?

Unless we're releasing those from some debugger function? But in that case we should be able to remove the releaseActor command, and remove the tests that are asserting the release of those actors.

Flags: needinfo?(jlaster)

we can safely remove the watchpoint logic, but should keep the rest

Flags: needinfo?(jlaster)

Stepan, looks like we have a clear view of what's needed now, do you want to pick that up?
No worries if you don't or can!

Flags: needinfo?(obdelnik)

I'd prefer not to work on this one if it is ok. I am not that familiar with this topic.

Flags: needinfo?(obdelnik)

sure, no worries, I'll take it then :)

Assignee: obdelnik → nchevobbe
Attachment #9125082 - Attachment is obsolete: true

The Reps bundle was directly edited, but the change
wasn't made in the original action file
Furthermore, changes made in Bug 1602804 were too
strict, as we still need to release actors when
we can.

Pushed by nchevobbe@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d9287eba3207
Fix ObjectInspector releaseActors action. r=jlast.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 75

Is this something we need on Beta for 74 or can this ride 75 to release?

Flags: needinfo?(nchevobbe)

not sure, what do you think Jason?

Flags: needinfo?(nchevobbe) → needinfo?(jlaster)

P3 and we shipped our last beta, so wontfix for 74.

Flags: needinfo?(jlaster)
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: