Bump betterproto2 from 0.9.1 to 0.10.0 #651
Annotations
15 errors and 9 warnings
|
Run Python Tests (3.13)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.13)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.13)
Permission denied when trying to create/update comment.
This error usually occurs because the GITHUB_TOKEN lacks necessary permissions.
To fix this, add a permissions block to your workflow:
```yaml
permissions:
contents: read # For checkout and comparing commits
pull-requests: write # For creating/updating PR comments
```
For pull request events and more information, see:
https://github.com/MishaKav/pytest-coverage-comment#comment-not-appearing
|
|
Run Python Tests (3.10)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.10)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.10)
Permission denied when trying to create/update comment.
This error usually occurs because the GITHUB_TOKEN lacks necessary permissions.
To fix this, add a permissions block to your workflow:
```yaml
permissions:
contents: read # For checkout and comparing commits
pull-requests: write # For creating/updating PR comments
```
For pull request events and more information, see:
https://github.com/MishaKav/pytest-coverage-comment#comment-not-appearing
|
|
Run Python Tests (3.11)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.11)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.11)
Permission denied when trying to create/update comment.
This error usually occurs because the GITHUB_TOKEN lacks necessary permissions.
To fix this, add a permissions block to your workflow:
```yaml
permissions:
contents: read # For checkout and comparing commits
pull-requests: write # For creating/updating PR comments
```
For pull request events and more information, see:
https://github.com/MishaKav/pytest-coverage-comment#comment-not-appearing
|
|
Run Python Tests (3.12)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.12)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.12)
Permission denied when trying to create/update comment.
This error usually occurs because the GITHUB_TOKEN lacks necessary permissions.
To fix this, add a permissions block to your workflow:
```yaml
permissions:
contents: read # For checkout and comparing commits
pull-requests: write # For creating/updating PR comments
```
For pull request events and more information, see:
https://github.com/MishaKav/pytest-coverage-comment#comment-not-appearing
|
|
Run Python Tests (3.14)
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.14)
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Run Python Tests (3.14)
Permission denied when trying to create/update comment.
This error usually occurs because the GITHUB_TOKEN lacks necessary permissions.
To fix this, add a permissions block to your workflow:
```yaml
permissions:
contents: read # For checkout and comparing commits
pull-requests: write # For creating/updating PR comments
```
For pull request events and more information, see:
https://github.com/MishaKav/pytest-coverage-comment#comment-not-appearing
|
|
Run Python Tests (3.13)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|
|
Run Python Tests (3.10)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-477dfab07df0d89350991f2b98b9e199fe84359ebb6b857e5521af707a4042a6, another job may be creating this cache.
|
|
Run Python Tests (3.10)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|
|
Run Python Tests (3.11)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-477dfab07df0d89350991f2b98b9e199fe84359ebb6b857e5521af707a4042a6, another job may be creating this cache.
|
|
Run Python Tests (3.11)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|
|
Run Python Tests (3.12)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-477dfab07df0d89350991f2b98b9e199fe84359ebb6b857e5521af707a4042a6, another job may be creating this cache.
|
|
Run Python Tests (3.12)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|
|
Run Python Tests (3.14)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-477dfab07df0d89350991f2b98b9e199fe84359ebb6b857e5521af707a4042a6, another job may be creating this cache.
|
|
Run Python Tests (3.14)
Your comment is too long (maximum is 65536 characters), coverage report will not be added.
Try one/some of the following options:
- Add "--cov-report=term-missing:skip-covered" to pytest command
- Add "hide-report: true" to hide detailed coverage table
- Add "report-only-changed-files: true" to show only changed files
- Add "xml-skip-covered: true" to hide files with 100% coverage
- Switch to "multiple-files" mode
- Add "remove-links-to-files: true" to remove file links
- Add "remove-links-to-lines: true" to remove line number links
|