Closed
Bug 1083142
Opened 11 years ago
Closed 11 years ago
Reference to undefined property this.nextConnID in marionette-server.js
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla36
People
(Reporter: ato, Assigned: kjjcrm1, Mentored)
Details
Attachments
(1 file)
|
999 bytes,
patch
|
ato
:
review+
|
Details | Diff | Splinter Review |
The following error is outputted to gecko.log:
JavaScript strict warning: chrome://marionette/content/marionette-server.js, line 2975: ReferenceError: reference to undefined property this.nextConnID
| Reporter | ||
Updated•11 years ago
|
Whiteboard: [good first bug] [mentor=ato]
Hi Iam interested in this bug, could you please tell me more about this bug and where its causing issues? Thanks
| Reporter | ||
Comment 2•11 years ago
|
||
Hi Jesal, and welcome!
The marionette-server.js file that is referenced above is located in testing/marionette/marionette-server.js in the mozilla-central repo. If you look at line 2976 (http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-server.js#2976) it increments the nextConnID counter for every new client connection that is made.
The ReferenceError gets outputted to gecko.log when you make a new connection to Marionette. The error is complaining that the property nextConnID on the this reference object doesn't exist. If we look at line 2964 (http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-server.js#2964) we can see it's defined as “nextConnId”, that is with a small “d” at the end; so the call on line 2976 is wrong.
This is a one character fix.
(In reply to Andreas Tolfsen (:ato) from comment #2)
> Hi Jesal, and welcome!
>
> The marionette-server.js file that is referenced above is located in
> testing/marionette/marionette-server.js in the mozilla-central repo. If you
> look at line 2976
> (http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-
> server.js#2976) it increments the nextConnID counter for every new client
> connection that is made.
>
> The ReferenceError gets outputted to gecko.log when you make a new
> connection to Marionette. The error is complaining that the property
> nextConnID on the this reference object doesn't exist. If we look at line
> 2964
> (http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-
> server.js#2964) we can see it's defined as “nextConnId”, that is with a
> small “d” at the end; so the call on line 2976 is wrong.
>
> This is a one character fix.
Thanks Andreas, I will get working on a patch now and will upload it here when it's done.
Will you assign the bug once the patch is done?
Thanks for your advice.
Jesal
| Reporter | ||
Comment 4•11 years ago
|
||
Done. I'm ato in #ateam on IRC if you need any help.
Assignee: nobody → kjjcrm1
Status: NEW → ASSIGNED
(In reply to Andreas Tolfsen (:ato) from comment #4)
> Done. I'm ato in #ateam on IRC if you need any help.
Thanks, great to know you are on the IRC
I am working on the patch and will have it uploaded today.
Thanks
Hi Andreas, here is my patch. Please review this and check if I need to do anything else? If its ok, what happens next?
Thanks
Jesal
Attachment #8507765 -
Flags: review?(ato)
| Reporter | ||
Comment 8•11 years ago
|
||
Comment on attachment 8507765 [details] [diff] [review]
bug1083142.patch This is hopefully the fix for the bug?
Review of attachment 8507765 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks, this indeed fixes the problem!
Attachment #8507765 -
Flags: review?(ato) → review+
| Reporter | ||
Updated•11 years ago
|
Keywords: checkin-needed
Whiteboard: [good first bug] [mentor=ato]
Comment 9•11 years ago
|
||
Keywords: checkin-needed
| Assignee | ||
Comment 10•11 years ago
|
||
(In reply to Andreas Tolfsen (:ato) from comment #8)
> Comment on attachment 8507765 [details] [diff] [review]
> bug1083142.patch This is hopefully the fix for the bug?
>
> Review of attachment 8507765 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> Thanks, this indeed fixes the problem!
Thats great thanks Andreas. So what are the next steps? I understand that the patch will be pushed to fxteam first then loaded into Mozilla-central? do I need to do anything further to help this?
Also Can I start working on another bug straight away, or do i need to pull change from Mozilla into my central directory?
Thanks
Jesal
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
Updated•3 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•