Skip to content
Run mypy_primer on PR

Skip keyword-only params with invalid names in signature help #1550

Sign in to view logs

Skip keyword-only params with invalid names in signature help

Skip keyword-only params with invalid names in signature help #1550

Triggered via pull request November 7, 2024 00:49
@debontedebonte
synchronize #9398
debonte:invalidAlias
Status Cancelled
Total duration 2m 9s
Artifacts –

mypy_primer_pr.yaml

on: pull_request
Matrix: Run mypy_primer on PR
Fit to window
Zoom out
Zoom in

Annotations

16 errors
Run mypy_primer on PR (1)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (1)
The operation was canceled.
Run mypy_primer on PR (4)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (4)
The operation was canceled.
Run mypy_primer on PR (7)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (7)
The operation was canceled.
Run mypy_primer on PR (5)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (5)
The operation was canceled.
Run mypy_primer on PR (3)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (3)
The operation was canceled.
Run mypy_primer on PR (6)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (6)
The operation was canceled.
Run mypy_primer on PR (2)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (2)
The operation was canceled.
Run mypy_primer on PR (0)
Canceling since a higher priority waiting request for 'Run mypy_primer on PR-invalidAlias' exists
Run mypy_primer on PR (0)
The operation was canceled.