Python AfterAny, AfterAll do not follow spec

[damccorm]

Both AfterAll and AfterAny should complete after firing, but they base their logic on the subtriggers, but they instead only finish if all the fired subtriggers or any of the fired subtriggers finish. This makes it possible for them to never finish.

For more info, see discussion in https://github.com/apache/beam/pull/15603

Imported from Jira BEAM-13076. Original Jira may contain additional context. Reported by: zhoufek.

[kennknowles]

@zhoufek did you follow up with this, or is it still outstanding?

[johnjcasey]

I've been looking into this, and it is starting to seem like python triggers need to be reworked to some extent

[johnjcasey]

it looks like afterAny simply doesn't fire correctly at all, and has never done so

[kennknowles]

@johnjcasey are you working on this still?

[johnjcasey]

I am not, I wasn't able to understand how python triggers work (or dont) in the fixit week.