4 ms·
Oh god yeah. It really sucks. This is going to be a pain with anything async right now though.
by ulisesrmzroche 13y ago
Oh god yeah. It really sucks. This is going to be a pain with anything async right now though.
- mjallday 13y agoI assume there's a way to add context information into the run loop when firing events for debugging purposes. This would largely solve the first half of the issue (who fired the event). The second half, where the error happened, seems like it's just a bug in the way Ember is recording errors.
- ulisesrmzroche 13y agoThis I'm not too sure about. I know they're moving this to https://github.com/ebryn/backburner.js https://github.com/ebryn/backburner.js. I'll read through the code sometime tonight and figure out what's going on.