Christian

I noticed a similar issue when using the `will-destroy` render modifier. Given two components, one using `@ember/component` (`Foo`) and one using `@glimmer/component` (`Bar`). Component impl: ```js export default class Foo...

Is there a hook for glimmer components to execute when it will destroy but is still in DOM? I noticed that basic-dropdown (maybe cc @cibernox ) (see [template](https://github.com/cibernox/ember-basic-dropdown/blob/master/addon/templates/components/basic-dropdown-content.hbs#L20) ) does...

Sounds interesting. Do you have any examples on how it should look like? (I've never worked with ICC profiles). From the linked issue i found that one can create named...

As it turns out, the 500 disappears if i artificially reduce the test results size in the [qunit_adapter](https://github.com/testem/testem/blob/master/public/testem/qunit_adapter.js#L112) before emitting the event. With minimizing the payload to: ``` results.tests =...

I can also confirm that it now works on IE 11. My theory is that saucelabs connect somehow fails if we send too much data over the POST that gets...

@johanneswuerbach does testem need the data in the `all-test-results` event? I've found a listener for it in the following places: - https://github.com/testem/testem/blob/b3bc9896a3f68fe8b25c495881f5ef3807624b6e/lib/runners/browser_test_runner.js#L182 - https://github.com/testem/testem/blob/bc28d03ffcd27fbe681a367ab59a4ac61a9cf382/lib/runners/tap_process_test_runner.js#L45 Both of them ignore the functions...

I think there's still the issue that a single `test-result` can get too long. The completing test above was a subset of our tests. If i run it on the...

I had some time to investigate it further. After some exchange with the saucelabs team, I've updated to sauceconnect 4.4.9 (most recent version). Sadly this didn't solve the issue. I've...

Just a small update: After writing back and forth with the sauce support, we haven't found the issue yet. My current best guess is that it's something related to their...

The only update i can give is that they moved the issue from general support to the development team. Sadly the only update we've got after that was "We're working...