Skip to content

nojump.py raises a valueerror when applied not at first frame #3367

nojump.py raises a valueerror when applied not at first frame

nojump.py raises a valueerror when applied not at first frame #3367

Triggered via pull request January 4, 2026 10:51
Status Cancelled
Total duration 1m 7s
Artifacts

linters.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 errors
black
Canceling since a higher priority waiting request for refs/pull/5201/merge-nojump_fail_outside_0-linters exists
mypy
Canceling since a higher priority waiting request for refs/pull/5201/merge-nojump_fail_outside_0-linters exists
mypy
The operation was canceled.
linters
Canceling since a higher priority waiting request for refs/pull/5201/merge-nojump_fail_outside_0-linters exists
pylint_check
Canceling since a higher priority waiting request for refs/pull/5201/merge-nojump_fail_outside_0-linters exists
pylint_check
The operation was canceled.