Skip to content

File operations

File operations #61

Re-run triggered September 30, 2023 18:06
Status Failure
Total duration 38s
Artifacts

on_pull_request.yml

on: pull_request
reviewdog
27s
reviewdog
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
reviewdog: examples/python_client_library/file_operations.py#L38
[] reported by reviewdog 🐶 C0301: Line too long (102/100) (line-too-long) Raw Output: python_client_library/file_operations.py:38:0: C0301: Line too long (102/100) (line-too-long)
reviewdog: examples/python_client_library/file_operations.py#L99
[] reported by reviewdog 🐶 C0301: Line too long (126/100) (line-too-long) Raw Output: python_client_library/file_operations.py:99:0: C0301: Line too long (126/100) (line-too-long)
reviewdog: examples/python_client_library/file_operations.py#L108
[] reported by reviewdog 🐶 C0304: Final newline missing (missing-final-newline) Raw Output: python_client_library/file_operations.py:108:0: C0304: Final newline missing (missing-final-newline)
reviewdog: examples/python_client_library/file_operations.py#L1
[] reported by reviewdog 🐶 C0114: Missing module docstring (missing-module-docstring) Raw Output: python_client_library/file_operations.py:1:0: C0114: Missing module docstring (missing-module-docstring)
reviewdog: examples/python_client_library/file_operations.py#L18
[] reported by reviewdog 🐶 C0103: Variable name "f" doesn't conform to snake_case naming style (invalid-name) Raw Output: python_client_library/file_operations.py:18:8: C0103: Variable name "f" doesn't conform to snake_case naming style (invalid-name)
reviewdog: examples/python_client_library/file_operations.py#L19
[] reported by reviewdog 🐶 R1714: Consider merging these comparisons with 'in' by using 'f.name not in ('.', '..')'. Use a set instead if elements are hashable. (consider-using-in) Raw Output: python_client_library/file_operations.py:19:11: R1714: Consider merging these comparisons with 'in' by using 'f.name not in ('.', '..')'. Use a set instead if elements are hashable. (consider-using-in)
reviewdog: examples/python_client_library/file_operations.py#L37
[] reported by reviewdog 🐶 W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation) Raw Output: python_client_library/file_operations.py:37:8: W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation)
reviewdog: examples/python_client_library/file_operations.py#L49
[] reported by reviewdog 🐶 W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation) Raw Output: python_client_library/file_operations.py:49:8: W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation)
reviewdog: examples/python_client_library/file_operations.py#L53
[] reported by reviewdog 🐶 C0116: Missing function or method docstring (missing-function-docstring) Raw Output: python_client_library/file_operations.py:53:0: C0116: Missing function or method docstring (missing-function-docstring)
reviewdog
reviewdog: Too many results (annotations) in diff. You may miss some annotations due to GitHub limitation for annotation created by logging command. Please check GitHub Actions log console to see all results. Limitation: - 10 warning annotations and 10 error annotations per step - 50 annotations per job (sum of annotations from all the steps) - 50 annotations per run (separate from the job annotations, these annotations aren't created by users) Source: https://github.community/t5/GitHub-Actions/Maximum-number-of-annotations-that-can-be-created-using-GitHub/m-p/39085
reviewdog
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/