⬆ Bump tenacity from 8.2.3 to 9.0.0 #59

dependabot · 2024-09-28T16:17:05Z

Bumps tenacity from 8.2.3 to 9.0.0.

Release notes

tenacity 9.0.0

What's Changed

Respects min argument for wait_random_exponential by @yxtay in jd/tenacity#425

Bump major version to warn API breakage on statistics attribute

Full Changelog: jd/tenacity@8.5.0...9.0.0

8.5.0

What's Changed

fix: Restore contents of retry attribute for wrapped functions by @hasier in jd/tenacity#484

Full Changelog: jd/tenacity@8.4.2...8.5.0

tenacity 8.4.2

What's Changed

fix: Avoid overwriting local contexts with retry decorator by @hasier in jd/tenacity#479

Full Changelog: jd/tenacity@8.4.1...8.4.2

tenacity 8.4.1

What's Changed

Include tenacity.asyncio subpackage in release dist by @cdce8p in jd/tenacity#474

Full Changelog: jd/tenacity@8.4.0...8.4.1

tenacity 8.4.0

What's Changed

Add async strategies by @hasier in jd/tenacity#451

Support Trio out-of-the-box by @jakkdl in jd/tenacity#463

Full Changelog: jd/tenacity@8.3.0...8.4.0

8.3.0

New Features

Added a new stop function: stop_before_delay, which will stop execution if the next sleep time would cause overall delay to exceed the specified delay. Useful for use cases where you have some upper bound on retry times that you must not exceed, so returning before that timeout is preferable than returning after that timeout.

Bug Fixes

Preserve defaults and kwdefaults through retry decorator

Other Notes

Add a "test" extra

Commits

a662bbb Respects min argument for wait_random_exponential (#425)
31fe2d0 fix: Restore contents of retry attribute for wrapped functions (#484)
33cd0e1 chore(deps): bump actions/checkout in the github-actions group (#483)
a15fa64 fix: Avoid overwriting local contexts with retry decorator (#479)
ee6a8f7 Include tenacity.asyncio subpackage in release dist (#474)
702014b ci: add support for trio in Mergify automerge (#470)
ade0567 Support Trio out-of-the-box, take 2 (#463)
952189b Update index.rst: Remove * (#465)
5b00c15 chore(deps): bump the github-actions group across 1 directory with 2 updates ...
21137e7 Add async strategies (#451)
Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

sourcery-ai

We have skipped reviewing this pull request. Here's why:

It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
We don't review packaging changes - Let us know if you'd like us to change this.

qodo-merge-pro · 2024-09-28T16:18:08Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build-and-test
Failed stage: Build dev docker [❌]
Failure summary: The action failed due to a dependency conflict during the installation of packages: `pr-insight` version 0.2.4 requires `tenacity==9.0.0`. `chromadb` version 0.5.7 requires `tenacity>=8.2.3`. `langchain` version 0.3.0 requires `tenacity!=8.4.0, <9.0.0 and >=8.1.0`. These conflicting requirements for the `tenacity` package made it impossible for pip to resolve dependencies.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1051: #12 18.56 Collecting langchain-text-splitters<0.4.0,>=0.3.0 (from langchain==0.3.0->pr-insight==0.2.4) 1052: #12 18.57 Downloading langchain_text_splitters-0.3.0-py3-none-any.whl.metadata (2.3 kB) 1053: #12 18.70 Collecting langsmith<0.2.0,>=0.1.17 (from langchain==0.3.0->pr-insight==0.2.4) 1054: #12 18.71 Downloading langsmith-0.1.129-py3-none-any.whl.metadata (13 kB) 1055: #12 18.73 Collecting numpy>=1.22.5 (from chromadb==0.5.7->pr-insight==0.2.4) 1056: #12 18.73 Downloading numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB) 1057: #12 18.74 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.0/61.0 kB 11.5 MB/s eta 0:00:00 1058: #12 18.80 INFO: pip is looking at multiple versions of langchain to determine which version is compatible with other requirements. This could take a while. 1059: #12 19.02 ERROR: Cannot install pr-insight and pr-insight==0.2.4 because these package versions have conflicting dependencies. ... 1062: #12 19.02 pr-insight 0.2.4 depends on tenacity==9.0.0 1063: #12 19.02 chromadb 0.5.7 depends on tenacity>=8.2.3 1064: #12 19.02 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1065: #12 19.02 1066: #12 19.02 To fix this you could try to: 1067: #12 19.02 1. loosen the range of package versions you've specified 1068: #12 19.02 2. remove package versions to allow pip attempt to solve the dependency conflict 1069: #12 19.02 1070: #12 19.02 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 1071: #12 19.03 1072: #12 19.03 [notice] A new release of pip is available: 24.0 -> 24.2 1073: #12 19.03 [notice] To update, run: pip install --upgrade pip 1074: #12 ERROR: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1075: ------ 1076: > [base 6/6] RUN pip install . && rm pyproject.toml requirements.txt: 1077: 19.02 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1078: 19.02 1079: 19.02 To fix this you could try to: 1080: 19.02 1. loosen the range of package versions you've specified 1081: 19.02 2. remove package versions to allow pip attempt to solve the dependency conflict 1082: 19.02 1083: 19.02 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts ... 1088: Dockerfile:7 1089: -------------------- 1090: 5 \| ADD pyproject.toml . 1091: 6 \| ADD requirements.txt . 1092: 7 \| >>> RUN pip install . && rm pyproject.toml requirements.txt 1093: 8 \| ENV PYTHONPATH=/app 1094: 9 \| 1095: -------------------- 1096: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1097: ##[error]buildx failed with: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: 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.

qodo-merge-pro · 2024-09-28T16:18:27Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build-and-test
Failed stage: Build dev docker [❌]
Failure summary: The action failed due to a dependency conflict during the installation of packages: The package `pr-insight` version 0.2.4 requires `tenacity==9.0.0`. The package `chromadb` version 0.5.7 requires `tenacity>=8.2.3`. The package `langchain` version 0.3.0 requires `tenacity!=8.4.0, <9.0.0 and >=8.1.0`. These conflicting requirements for the `tenacity` package made it impossible for pip to resolve dependencies, resulting in a `ResolutionImpossible` error.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1101: #12 16.18 Collecting langchain-text-splitters<0.4.0,>=0.3.0 (from langchain==0.3.0->pr-insight==0.2.4) 1102: #12 16.19 Downloading langchain_text_splitters-0.3.0-py3-none-any.whl.metadata (2.3 kB) 1103: #12 16.31 Collecting langsmith<0.2.0,>=0.1.17 (from langchain==0.3.0->pr-insight==0.2.4) 1104: #12 16.32 Downloading langsmith-0.1.129-py3-none-any.whl.metadata (13 kB) 1105: #12 16.33 Collecting numpy>=1.22.5 (from chromadb==0.5.7->pr-insight==0.2.4) 1106: #12 16.34 Downloading numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB) 1107: #12 16.34 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.0/61.0 kB 18.0 MB/s eta 0:00:00 1108: #12 16.41 INFO: pip is looking at multiple versions of langchain to determine which version is compatible with other requirements. This could take a while. 1109: #12 16.62 ERROR: Cannot install pr-insight and pr-insight==0.2.4 because these package versions have conflicting dependencies. ... 1112: #12 16.62 pr-insight 0.2.4 depends on tenacity==9.0.0 1113: #12 16.62 chromadb 0.5.7 depends on tenacity>=8.2.3 1114: #12 16.62 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1115: #12 16.62 1116: #12 16.62 To fix this you could try to: 1117: #12 16.62 1. loosen the range of package versions you've specified 1118: #12 16.62 2. remove package versions to allow pip attempt to solve the dependency conflict 1119: #12 16.62 1120: #12 16.62 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 1121: #12 16.63 1122: #12 16.63 [notice] A new release of pip is available: 24.0 -> 24.2 1123: #12 16.63 [notice] To update, run: pip install --upgrade pip 1124: #12 ERROR: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1125: ------ 1126: > [base 6/6] RUN pip install . && rm pyproject.toml requirements.txt: 1127: 16.62 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1128: 16.62 1129: 16.62 To fix this you could try to: 1130: 16.62 1. loosen the range of package versions you've specified 1131: 16.62 2. remove package versions to allow pip attempt to solve the dependency conflict 1132: 16.62 1133: 16.62 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts ... 1138: Dockerfile:7 1139: -------------------- 1140: 5 \| ADD pyproject.toml . 1141: 6 \| ADD requirements.txt . 1142: 7 \| >>> RUN pip install . && rm pyproject.toml requirements.txt 1143: 8 \| ENV PYTHONPATH=/app 1144: 9 \| 1145: -------------------- 1146: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1147: ##[error]buildx failed with: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: 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.

Bumps [tenacity](https://github.com/jd/tenacity) from 8.2.3 to 9.0.0. - [Release notes](https://github.com/jd/tenacity/releases) - [Commits](jd/tenacity@8.2.3...9.0.0) --- updated-dependencies: - dependency-name: tenacity dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

qodo-merge-pro · 2024-10-05T01:08:47Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build-and-test
Failed stage: Build dev docker [❌]
Failed test name: ""
Failure summary: The action failed due to a dependency conflict during the installation of Python packages: The package `pr-insight==0.2.4` requires `tenacity==9.0.0`. The package `chromadb==0.5.7` requires `tenacity>=8.2.3`. The package `langchain==0.3.0` requires `tenacity!=8.4.0, <9.0.0 and >=8.1.0`. These conflicting requirements for the `tenacity` package made it impossible for the dependency resolver to find a compatible version, resulting in a `ResolutionImpossible` error.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1041: #12 17.55 Collecting langchain-text-splitters<0.4.0,>=0.3.0 (from langchain==0.3.0->pr-insight==0.2.4) 1042: #12 17.55 Downloading langchain_text_splitters-0.3.0-py3-none-any.whl.metadata (2.3 kB) 1043: #12 17.68 Collecting langsmith<0.2.0,>=0.1.17 (from langchain==0.3.0->pr-insight==0.2.4) 1044: #12 17.69 Downloading langsmith-0.1.131-py3-none-any.whl.metadata (13 kB) 1045: #12 17.71 Collecting numpy>=1.22.5 (from chromadb==0.5.7->pr-insight==0.2.4) 1046: #12 17.72 Downloading numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB) 1047: #12 17.72 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.0/61.0 kB 16.9 MB/s eta 0:00:00 1048: #12 17.77 INFO: pip is looking at multiple versions of langchain to determine which version is compatible with other requirements. This could take a while. 1049: #12 17.98 ERROR: Cannot install pr-insight and pr-insight==0.2.4 because these package versions have conflicting dependencies. ... 1052: #12 17.98 pr-insight 0.2.4 depends on tenacity==9.0.0 1053: #12 17.98 chromadb 0.5.7 depends on tenacity>=8.2.3 1054: #12 17.98 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1055: #12 17.98 1056: #12 17.98 To fix this you could try to: 1057: #12 17.98 1. loosen the range of package versions you've specified 1058: #12 17.98 2. remove package versions to allow pip attempt to solve the dependency conflict 1059: #12 17.98 1060: #12 17.98 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 1061: #12 17.99 1062: #12 17.99 [notice] A new release of pip is available: 24.0 -> 24.2 1063: #12 17.99 [notice] To update, run: pip install --upgrade pip 1064: #12 ERROR: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1065: ------ 1066: > [base 6/6] RUN pip install . && rm pyproject.toml requirements.txt: 1067: 17.98 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1068: 17.98 1069: 17.98 To fix this you could try to: 1070: 17.98 1. loosen the range of package versions you've specified 1071: 17.98 2. remove package versions to allow pip attempt to solve the dependency conflict 1072: 17.98 1073: 17.98 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts ... 1078: Dockerfile:7 1079: -------------------- 1080: 5 \| ADD pyproject.toml . 1081: 6 \| ADD requirements.txt . 1082: 7 \| >>> RUN pip install . && rm pyproject.toml requirements.txt 1083: 8 \| ENV PYTHONPATH=/app 1084: 9 \| 1085: -------------------- 1086: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1087: ##[error]buildx failed with: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: 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.

qodo-merge-pro · 2024-10-05T01:09:07Z

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build-and-test
Failed stage: Build dev docker [❌]
Failure summary: The action failed due to a dependency conflict during the installation of Python packages: The package `pr-insight` version 0.2.4 requires `tenacity` version 9.0.0. The package `chromadb` version 0.5.7 requires `tenacity` version 8.2.3 or higher. The package `langchain` version 0.3.0 requires `tenacity` version not equal to 8.4.0, less than 9.0.0, and greater than or equal to 8.1.0. These conflicting requirements for the `tenacity` package make it impossible for the dependency resolver to find a compatible version.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1054: #12 18.33 Collecting langchain-text-splitters<0.4.0,>=0.3.0 (from langchain==0.3.0->pr-insight==0.2.4) 1055: #12 18.35 Downloading langchain_text_splitters-0.3.0-py3-none-any.whl.metadata (2.3 kB) 1056: #12 18.47 Collecting langsmith<0.2.0,>=0.1.17 (from langchain==0.3.0->pr-insight==0.2.4) 1057: #12 18.48 Downloading langsmith-0.1.131-py3-none-any.whl.metadata (13 kB) 1058: #12 18.50 Collecting numpy>=1.22.5 (from chromadb==0.5.7->pr-insight==0.2.4) 1059: #12 18.52 Downloading numpy-1.26.4-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB) 1060: #12 18.52 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.0/61.0 kB 19.6 MB/s eta 0:00:00 1061: #12 18.58 INFO: pip is looking at multiple versions of langchain to determine which version is compatible with other requirements. This could take a while. 1062: #12 18.80 ERROR: Cannot install pr-insight and pr-insight==0.2.4 because these package versions have conflicting dependencies. ... 1065: #12 18.80 pr-insight 0.2.4 depends on tenacity==9.0.0 1066: #12 18.80 chromadb 0.5.7 depends on tenacity>=8.2.3 1067: #12 18.80 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1068: #12 18.80 1069: #12 18.80 To fix this you could try to: 1070: #12 18.80 1. loosen the range of package versions you've specified 1071: #12 18.80 2. remove package versions to allow pip attempt to solve the dependency conflict 1072: #12 18.80 1073: #12 18.80 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 1074: #12 18.81 1075: #12 18.81 [notice] A new release of pip is available: 24.0 -> 24.2 1076: #12 18.81 [notice] To update, run: pip install --upgrade pip 1077: #12 ERROR: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1078: ------ 1079: > [base 6/6] RUN pip install . && rm pyproject.toml requirements.txt: 1080: 18.80 langchain 0.3.0 depends on tenacity!=8.4.0, <9.0.0 and >=8.1.0 1081: 18.80 1082: 18.80 To fix this you could try to: 1083: 18.80 1. loosen the range of package versions you've specified 1084: 18.80 2. remove package versions to allow pip attempt to solve the dependency conflict 1085: 18.80 1086: 18.80 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts ... 1091: Dockerfile:7 1092: -------------------- 1093: 5 \| ADD pyproject.toml . 1094: 6 \| ADD requirements.txt . 1095: 7 \| >>> RUN pip install . && rm pyproject.toml requirements.txt 1096: 8 \| ENV PYTHONPATH=/app 1097: 9 \| 1098: -------------------- 1099: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: exit code: 1 1100: ##[error]buildx failed with: ERROR: failed to solve: process "/bin/sh -c pip install . && rm pyproject.toml requirements.txt" did not complete successfully: 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.

dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Sep 28, 2024

sourcery-ai bot reviewed Sep 28, 2024

View reviewed changes

dependabot bot force-pushed the dependabot/pip/tenacity-9.0.0 branch from aa6d5d8 to 65b001c Compare October 5, 2024 01:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

⬆ Bump tenacity from 8.2.3 to 9.0.0 #59

⬆ Bump tenacity from 8.2.3 to 9.0.0 #59

dependabot bot commented on behalf of github Sep 28, 2024 •

edited

Loading

sourcery-ai bot left a comment

qodo-merge-pro bot commented Sep 28, 2024

Configuration options

qodo-merge-pro bot commented Sep 28, 2024

Configuration options

qodo-merge-pro bot commented Oct 5, 2024

Configuration options

qodo-merge-pro bot commented Oct 5, 2024

Configuration options

⬆ Bump tenacity from 8.2.3 to 9.0.0 #59

Are you sure you want to change the base?

⬆ Bump tenacity from 8.2.3 to 9.0.0 #59

Conversation

dependabot bot commented on behalf of github Sep 28, 2024 • edited Loading

tenacity 9.0.0

What's Changed

8.5.0

What's Changed

tenacity 8.4.2

What's Changed

tenacity 8.4.1

What's Changed

tenacity 8.4.0

What's Changed

8.3.0

New Features

Bug Fixes

Other Notes

sourcery-ai bot left a comment

Choose a reason for hiding this comment

qodo-merge-pro bot commented Sep 28, 2024

CI Failure Feedback 🧐

Configuration options

qodo-merge-pro bot commented Sep 28, 2024

CI Failure Feedback 🧐

Configuration options

qodo-merge-pro bot commented Oct 5, 2024

CI Failure Feedback 🧐

Configuration options

qodo-merge-pro bot commented Oct 5, 2024

CI Failure Feedback 🧐

Configuration options

dependabot bot commented on behalf of github Sep 28, 2024 •

edited

Loading