Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typescript changes for Beam 2.51.0 #28553

Merged
merged 3 commits into from
Sep 20, 2023
Merged

Typescript changes for Beam 2.51.0 #28553

merged 3 commits into from
Sep 20, 2023

Conversation

robertwb
Copy link
Contributor

  • Bad dependbot upgrades.
  • Missing experiments due to Python dataflow runner change.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

If we upgrade proto, we need to regenerate the protos.
This is probably related to BEAM-28399; best to fix here to be explicit.
@robertwb
Copy link
Contributor Author

R: @kennknowles

@github-actions
Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

@@ -33,6 +33,8 @@ export function dataflowRunner(runnerOptions: {
options: Object = {}
): Promise<PipelineResult> {
var augmentedOptions = { experiments: [] as string[], ...options };
augmentedOptions.experiments.push("use_runner_v2");
augmentedOptions.experiments.push("use_portable_job_submission");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would typescript tests have caught this? If yes, should we add python runner paths to the workflow trigger so that the tests run against python dataflow runner changes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the TypeScript Dataflow Tests should have caught this, but it's not generally run due to lack of credentials.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but it's not generally run due to lack of credentials.

Not sure what this means - https://github.com/apache/beam/actions/workflows/typescript_tests.yml looks like its running consistently

sdks/typescript/package.json Outdated Show resolved Hide resolved
@damccorm damccorm merged commit 3b7e1dc into apache:master Sep 20, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants