You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firefox 69 now emits the unhandledrejection event by default. Unfortunately, there’s a bug where the unhandled rejection event is emitted when source.start() rejects from new ReadableStream(source). This bug affects this test:
assert.strictEqual(errorCaught,true,"malformed json string should cause an error");
done();
},function(){
assert.strictEqual(errorCaught,true,"rejected: malformed json string should cause an error");
done();
});
});
I don’t think we can do anything about this, so for the purposes of testing, I think we should work around it by adding QUnit.onUnhandledRejection = function() {} to our test so the unhandled rejection is “handled” and the tests don’t fail in Firefox 69.
The alternative is to change the main CanJS test suite to run Firefox 68 until this bug gets fixed, but I think that’s a worse alternative because I don’t think we should test against an older version of Firefox just because of this issue.
The text was updated successfully, but these errors were encountered:
Firefox 69 now emits the
unhandledrejection
event by default. Unfortunately, there’s a bug where the unhandled rejection event is emitted whensource.start()
rejects fromnew ReadableStream(source)
. This bug affects this test:can-ndjson-stream/can-ndjson-stream-test.js
Lines 89 to 116 in abbffd2
I don’t think we can do anything about this, so for the purposes of testing, I think we should work around it by adding
QUnit.onUnhandledRejection = function() {}
to our test so the unhandled rejection is “handled” and the tests don’t fail in Firefox 69.The alternative is to change the main CanJS test suite to run Firefox 68 until this bug gets fixed, but I think that’s a worse alternative because I don’t think we should test against an older version of Firefox just because of this issue.
The text was updated successfully, but these errors were encountered: