[Snyk] Security upgrade requests from 2.31.0 to 2.32.0

[terrorizer1980]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • sdks/python/apache_beam/testing/benchmarks/chicago_taxi/requirements.txt

⚠️ Warning

tensorflow-transform 0.13.0 has requirement absl-py<2,>=0.1.6, but you have absl-py 2.1.0.
tensorflow-transform 0.13.0 has requirement protobuf<4,>=3.7, but you have protobuf 4.24.4.
tensorflow-model-analysis 0.13.2 has requirement ipywidgets<8,>=7, but you have ipywidgets 8.1.2.
tensorflow-model-analysis 0.13.2 has requirement protobuf<4,>=3.7, but you have protobuf 4.24.4.
tensorflow-metadata 0.13.0 has requirement protobuf<4,>=3.7, but you have protobuf 4.24.4.
tensorflow-data-validation 0.13.1 has requirement absl-py<1,>=0.1.6, but you have absl-py 2.1.0.
tensorflow-data-validation 0.13.1 has requirement protobuf<4,>=3.7, but you have protobuf 4.24.4.
qtconsole 5.4.4 requires pyzmq, which is not installed.
notebook 5.7.16 requires pyzmq, which is not installed.
notebook 5.7.16 has requirement nbconvert<6.0, but you have nbconvert 7.6.0.
jupyter-console 6.6.3 requires pyzmq, which is not installed.
jupyter-console 6.6.3 has requirement jupyter-client>=7.0.0, but you have jupyter-client 6.2.0.
jupyter-client 6.2.0 requires pyzmq, which is not installed.
ipykernel 6.16.2 requires pyzmq, which is not installed.
apache-beam 2.48.0 has requirement protobuf<4.24.0,>=3.20.3, but you have protobuf 4.24.4.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	566/1000 Why? Recently disclosed, Has a fix available, CVSS 5.6	Always-Incorrect Control Flow Implementation SNYK-PYTHON-REQUESTS-6928867	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[stale]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

[stale]

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.