Gino

This is specifically an incompatibility with `ember-cli-page-object` >= `v2.0.0-beta.4`. You can add a yarn resolution for `v2.0.0-beta.3` to work around the problem in the cleanest way possible. See https://github.com/Addepar/ember-classy-page-object/issues/39 for...

FYI https://github.com/Addepar/ember-classy-page-object/issues/39 was fixed and released, so if you use `ember-classy-page-object` `v0.8.0-beta.2` this problem should no longer happen. We can probably close this issue now.

I'm not sure. I don't think so.

Have you experienced this, or someone else? How often does it occur? I only listen to one SmartNet system, but so far I've only seen encrypted calls on the channels...

This was the top issue I was having with trunk-recorder. Agree that the numbering system is a mess but I'm happy there was a quick fix for this particular issue....

Rebased your branch and opened a PR. Thanks for fixing this, y'all. (edit: I removed the "fixes" from the description in case you want to keep this issue open for...

(Can the autofixer read rule options? Maybe it could be off by default and the fix strategy could be configurable.)

+1. We've been using it at Square with a huge monolith for nearly two years with no issues.

I agree with this as well. I also want to point out that given events like https://github.com/veged/coa/issues/99, `--no-lockfile` is a bit of a security issue too. A compromised package that...

Maybe this is worth adding a separate helper for? Then we could just trigger all of the events that the browser would trigger, and not care about whether or not...