You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 22:30:38 UTC
[GitHub] [beam] damccorm opened a new issue, #21262: Python AfterAny, AfterAll do not follow spec
damccorm opened a new issue, #21262:
URL: https://github.com/apache/beam/issues/21262
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](https://issues.apache.org/jira/browse/BEAM-13076). Original Jira may contain additional context.
Reported by: zhoufek.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] kennknowles commented on issue #21262: Python AfterAny, AfterAll do not follow spec
Posted by GitBox <gi...@apache.org>.
kennknowles commented on issue #21262:
URL: https://github.com/apache/beam/issues/21262#issuecomment-1341243427
@johnjcasey are you working on this still?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] johnjcasey commented on issue #21262: Python AfterAny, AfterAll do not follow spec
Posted by GitBox <gi...@apache.org>.
johnjcasey commented on issue #21262:
URL: https://github.com/apache/beam/issues/21262#issuecomment-1290837408
I've been looking into this, and it is starting to seem like python triggers need to be reworked to some extent
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] kennknowles commented on issue #21262: Python AfterAny, AfterAll do not follow spec
Posted by GitBox <gi...@apache.org>.
kennknowles commented on issue #21262:
URL: https://github.com/apache/beam/issues/21262#issuecomment-1246017630
@zhoufek did you follow up with this, or is it still outstanding?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] johnjcasey commented on issue #21262: Python AfterAny, AfterAll do not follow spec
Posted by GitBox <gi...@apache.org>.
johnjcasey commented on issue #21262:
URL: https://github.com/apache/beam/issues/21262#issuecomment-1290837983
it looks like afterAny simply doesn't fire correctly at all, and has never done so
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] johnjcasey commented on issue #21262: Python AfterAny, AfterAll do not follow spec
Posted by GitBox <gi...@apache.org>.
johnjcasey commented on issue #21262:
URL: https://github.com/apache/beam/issues/21262#issuecomment-1341417034
I am not, I wasn't able to understand how python triggers work (or dont) in the fixit week.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org