It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

This can fix the problem for sure, but I don't think simply making this change without understand how _lastPendingEventTimestamp can be null is a good idea. At the very least, we can't write a unit test for this PR.

@tarobins Can you please add a test for this?

(Triage): I am going to close this one since there was no follow-up. Looks like we have an issue on file to keep track of this work. If you (or anyone else) finds the time to work on this again, feel free to reopen. Thanks!