Bump google-cloud-webrisk from 1.15.0 to 1.16.0 in /requirements

[dependabot]

Bumps google-cloud-webrisk from 1.15.0 to 1.16.0.

Release notes

Sourced from google-cloud-webrisk's releases.

google-cloud-webrisk: v1.16.0

1.16.0 (2024-12-12)

Features

• Add support for opt-in debug logging (cf4d0e0)

Bug Fixes

• Fix typing issue with gRPC metadata when key ends in -bin (cf4d0e0)

Commits

• 20b8aaf chore: release main (#13297)
• d596268 feat: [google-cloud-monitoring] Added support for notification prompts in Ale...
• 19ed3be feat: [Many APIs] Add support for opt-in debug logging (#13343)
• 44761a8 chore: fix orchestration-airflow docs (#13355)
• d3e4f8d chore: fix docs for automl (#13354)
• 8b9c7bf feat: [Many APIs] Add support for opt-in debug logging (#13349)
• 1fcae7a chore: remove case-sensitive duplicate file (#13340)
• 11a3ff2 feat: add initial files for google.shopping.merchant.reviews.v1beta (#13351)
• feb5c03 feat: [Many APIs] Add support for opt-in debug logging (#13345)
• 819e8fb feat: [Many APIs] Add support for opt-in debug logging (#13344)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[deepsource-io]

Here's the code health analysis summary for commits 983802d..bce50a9. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

Action: backend-tests

Failed stage: Startup script launch (Fast) [❌]

Failure summary: The action failed due to Node.js version incompatibility: The build requires Node.js version ^20.17.0 || >=22.9.0 Current Node.js version is v20.13.1, which is too old Attempted to install [email protected] but failed due to the version mismatch The Docker build process failed during the frontend build step while trying to run npm install

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1892: #14 0.838 npm ERR! code EBADENGINE 1893: #14 0.839 npm ERR! engine Unsupported engine 1894: #14 0.839 npm ERR! engine Not compatible with your version of node/npm: [email protected] 1895: #14 0.840 npm ERR! notsup Not compatible with your version of node/npm: [email protected] 1896: #14 0.840 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1897: #14 0.840 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1898: #14 0.842 1899: #14 0.843 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-17T05_09_35_409Z-debug-0.log 1900: #14 ERROR: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 1901: ------ 1902: > [uwsgi frontend-build 4/5] RUN npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build: 1903: 0.838 npm ERR! code EBADENGINE 1904: 0.839 npm ERR! engine Unsupported engine 1905: 0.839 npm ERR! engine Not compatible with your version of node/npm: [email protected] 1906: failed to solve: process "/bin/sh -c npm install npm@latest --location=global && npm install && PUBLIC_URL=/static/reactapp/ npm run build" did not complete successfully: exit code: 1 1907: 0.840 npm ERR! notsup Not compatible with your version of node/npm: [email protected] 1908: 0.840 npm ERR! notsup Required: {"node":"^20.17.0 || >=22.9.0"} 1909: 0.840 npm ERR! notsup Actual: {"npm":"10.5.2","node":"v20.13.1"} 1910: 0.842 1911: 0.843 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-12-17T05_09_35_409Z-debug-0.log 1912: ------ 1913: ##[error]Process completed with exit code 17. 1914: ##[group]Run docker ps -a 1915: �[36;1mdocker ps -a�[0m 1916: �[36;1mdocker logs threatmatrix_uwsgi�[0m 1917: �[36;1mdocker logs threatmatrix_daphne�[0m 1918: shell: /usr/bin/bash -e {0} 1919: ##[endgroup] 1920: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1921: Error response from daemon: No such container: threatmatrix_uwsgi 1922: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)