Skip to content

Fix "Not enough arguments to" false positives on kwarg type checking #166

Fix "Not enough arguments to" false positives on kwarg type checking

Fix "Not enough arguments to" false positives on kwarg type checking #166

Triggered via pull request October 14, 2024 14:30
Status Success
Total duration 4m 21s
Artifacts

rspec.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (3.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/