We should be validating as much of our documentation as possible in
our testing, e.g.
https://github.com/apache/beam/tree/master/sdks/python/apache_beam/examples/snippets
is where the actual code and examples on our website (for Python)
lives to ensure it is regularly tested (on each PR) doesn't bi
Thanks for flagging this Joey, I reopened
https://github.com/apache/beam/issues/31624.
We can certainly validate any aspect of Beam during the release. I think it
should be possible to detect issues like this in a website/playground test
suite, and include that suite in the list of postcommit suit
There are a handful of bugs with the interactive examples on the Beam docs
page
https://beam.apache.org/documentation/transforms/python/elementwise/flatmap/#example-3-flatmap-without-a-function
https://beam.apache.org/documentation/transforms/python/elementwise/map/
(example 8)
I wonder if it mig
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/31725 The PostCommit Java
