GNOME Bugzilla – Bug 682290
Gio: Don't eat errors when trying to call the initial asyncCallback
Last modified: 2012-10-03 16:36:48 UTC
See patch. Turns out several JS errors were captured and went to the async error path, which is incorrect.
Created attachment 221878 [details] [review] Gio: Don't eat errors when trying to call the initial asyncCallback
Review of attachment 221878 [details] [review]: Good to go, if you want. ::: modules/overrides/Gio.js @@ +189,3 @@ if (asyncCallback) obj.init_async(GLib.PRIORITY_DEFAULT, cancellable, function(initable, result) { + let caughtErrorWhenInitting = null; Calling it error was too simple, heh? @@ +200,3 @@ + } else { + asyncCallback(null, caughtErrorWhenInitting); + log(caughtErrorWhenInitting); Why this log?
Review of attachment 221878 [details] [review]: ::: modules/overrides/Gio.js @@ +200,3 @@ + } else { + asyncCallback(null, caughtErrorWhenInitting); + log(caughtErrorWhenInitting); Because I left it in by accident.
Created attachment 225642 [details] [review] Gio: Don't eat errors when trying to call the initial asyncCallback
Review of attachment 225642 [details] [review]: Go go go!
Attachment 225642 [details] pushed as f2bef7e - Gio: Don't eat errors when trying to call the initial asyncCallback