Skip to content
No Response

Fix: Avoid the logout timer trying to acquire the lock twice #1877

Sign in to view logs

Fix: Avoid the logout timer trying to acquire the lock twice

Fix: Avoid the logout timer trying to acquire the lock twice #1877

Triggered via issue November 13, 2024 20:48
@fearnlj01fearnlj01
commented on #1200 4313d61
Status Success
Total duration 14s
Artifacts –

issue-no-response.yml

on: issue_comment
noResponse
5s
noResponse
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
noResponse
The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
noResponse
The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/