John Towler

Updated the original question with more complete code blocks

I've got a *very* ugly workaround, for now: Create a test helper ```js import Ember from 'ember'; import { it as originalIt } from 'mocha'; function it(label, func) { originalIt(label,...

Rendering is fine, it's only when you attempt to modify a component attribute that is being watched by an observer.

@PWKad We've been using the workaround from above successfully for the last 6 months.


The tests are done in that picture, but the completed percent shows as 0%, and the Mocha window is still yellow, because doesn't have class="finished"

That is the default reporter, as far as I can tell. I've done nothing but `ember install ember-cli-mocha` and `rm -rf node_modules && npm install`. Then I run `ember serve`...

We're moving from ember (non-cli) to ember-cli, and the current method of build/test for CI is the following: Build on build server Deploy to dev environment Run selenium from build...

`curl -L \ -X PATCH \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer $GH_TOKEN" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/repos/$ORG/$REPO \ -d '{"security_and_analysis":{"advanced_security":{"status":"enabled"}}}'` This is the equivalent cURL, and if...

> We are seeing this issue arise when running a `terraform apply` that requires modification to the repositories. Weirdly, running the apply again seems to bypass the issue. If the...