Justin Nguyen
Justin Nguyen
@seanlip There is also network error source which is formal errors from the network that are logged from the network such as 404, 500, etc. Should they be catched?
Hello, don't know if this is a good fix, but it seems that https://github.com/oppia/oppia/blob/08309f36ef4bda0fb6082d6de8638611d8e05f1b/core/templates/pages/exploration-editor-page/services/router.service.ts#L68 is called before the actual page is rendered, therefore the subscribe method in the settings page...
Oh the flakiness that I ran into wasn't actually caused by the PR I reverted but instead another issue to do with the feedback threads which was fixed in this...
@seanlip Are we looking to record everything? (all browsers (users) and full length) or like WDIO where it only records part of the failed run?
FYI @Akhilesh-max the root cause was mentioned here in this [comment](https://github.com/oppia/oppia/issues/19732#issuecomment-1975247680), given that this is a common flake, I suggest just waiting for the conversation skin for now /cc @seanlip.
Related to this issue #16413, should maybe resolve together.
@seanlip unassigned myself from the other issue BTW. The issues are related since you can't really test this issue without fixing the other issue since the "unexpected" console errors won't...
@HardikGoyal2003 Sorry for the late response, not currently working on this.