[v1.0-branch] Delivery of urgent events to subscriptions does not work correctly

[bzbarsky-apple]

If an urgent event is emitted at a point when the ReadHandler subscribing for it had already gotten its "min interval has elapsed" callback (very likely if it uses a short min-interval and a long max-interval), we just mark the read handler dirty but do not schedule a run of the reporting engine. This causes us to not report the event until something does trigger such a run (either the max interval being reached, or some other reading/reporting activity).

This pretty much breaks subscribing to urgent events with a large max-interval.

Fixed on tip by #23240 but still an issue on 1.0 branch.

[andy31415]

@bzbarsky-apple can this be closed? I see that github claims that a linked pulled request would close the issue ... but the PR is merged and the issue still open.

[bzbarsky-apple]

Yes, I don't know what the story is with github and links... it seems to only accept merges to master to close issues?