Skip to content
No Response

Adding custom elements to the DiagnosticsOverlay results in incorrect ordering #447

Sign in to view logs

Adding custom elements to the DiagnosticsOverlay results in incorrect ordering

Adding custom elements to the DiagnosticsOverlay results in incorrect ordering #447

Triggered via issue November 14, 2024 14:48
@dr1rrbdr1rrb
commented on #17838 e17cd40
Status Success
Total duration 10s
Artifacts –

no-response.yml

on: issue_comment
noResponse
2s
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/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb. 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/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/