Skip to content

Bugfix lagging MS response causing sequential moves to be dropped #300

Bugfix lagging MS response causing sequential moves to be dropped

Bugfix lagging MS response causing sequential moves to be dropped #300

Triggered via push October 12, 2024 17:25
Status Failure
Total duration 8h 26m 27s
Artifacts

prospector.yml

on: push
Run Prospector on all Python files
1m 37s
Run Prospector on all Python files
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Run Prospector on all Python files
Process completed with exit code 1.
Run Prospector on all Python files
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/
Run Prospector on all Python files
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/