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.

Sign up for GitHub

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

Jump to bottom

[Bug]: The Automated Beam Dependency Check Report is Empty #26896

Closed
15 tasks
jrmccluskey opened this issue May 25, 2023 · 0 comments · Fixed by #26954
Closed
15 tasks

[Bug]: The Automated Beam Dependency Check Report is Empty #26896

jrmccluskey opened this issue May 25, 2023 · 0 comments · Fixed by #26954
Assignees
@jrmccluskey
Labels
bug P3
Milestone
2.49.0 Release

Comments

@jrmccluskey
Copy link
Contributor

What happened?

The automated Beam Dependency Check Report email has been empty for some time, and the last successful run according to Jenkins was July 21st, 2022. The problem seems to be that the Python dependency check is failing, querying an IP address (which seems to go nowhere) looking specifically for Python 2 artifacts.

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jrmccluskey jrmccluskey

Labels
bug P3
Projects
None yet
Milestone
2.49.0 Release
1 participant
@jrmccluskey