I saw that while working in bug 1449162. It would be great to replace the cryptic exception happening within protocol.js by an explicit error message.

No impact on perf: https://treeherder.mozilla.org/perf.html#/comparesubtest?originalProject=try&originalRevision=6ca283f776f569d6f5e4a1805d8154e87f55f3af&newProject=try&newRevision=587d229b7062ed75bd70dffe2aa71095ce838952&originalSignature=f79b6a4f1f8f53326d3056f6c8008c0ff4de0a94&newSignature=f79b6a4f1f8f53326d3056f6c8008c0ff4de0a94&framework=1 Green try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=587d229b7062ed75bd70dffe2aa71095ce838952

Comment on attachment 8974317 [details] Bug 1460229 - Throw an explicit error message when a method specified in a spec is missing in the actor. https://reviewboard.mozilla.org/r/242634/#review250088 Great, this seems like a helpful improvement! :) ::: devtools/shared/protocol.js:1155 (Diff revision 1) > console.error("Error reading request: " + packet.type); > throw ex; > } > > + if (!this[spec.name]) { > + throw new Error(`Spec for '${actorProto.typeName}' specify a '${spec.name}' ` + Nit: specify -> specifies

Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ac313bdb1bff Throw an explicit error message when a method specified in a spec is missing in the actor. r=jryans