Skip to content

[Fix] Bugs where cleanup code is not executed correctly when bot exits #229

[Fix] Bugs where cleanup code is not executed correctly when bot exits

[Fix] Bugs where cleanup code is not executed correctly when bot exits #229

Re-run triggered September 26, 2025 14:10
Status Success
Total duration 1m 30s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
ruff
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+p7WaAAAAACmXQnzTpJETpG1NZUyC7LBREVOMzAxMDAwMTAxMDI1AEVkZ2U=
ruff
Failed to restore: Cache service responded with 400
pylint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0F5/WaAAAAAAxcspwEdspSq3v5t1iJ6auUEhYMzFFREdFMDUxNwBFZGdl
pylint
Failed to restore: Cache service responded with 400
pyright
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0CJ/WaAAAAABjNtN6kCVsRLc7efDKgUdPUEhMMzBFREdFMDIyMQBFZGdl
pyright
Failed to restore: Cache service responded with 400
mypy
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OJ/WaAAAAAA8zpXZ5zsYRIsftnyHIlurQ0hJMzBFREdFMDQxOQBFZGdl
mypy
Failed to restore: Cache service responded with 400