Skip to content

chore(deps): update node.js to v20 - autoclosed #30

chore(deps): update node.js to v20 - autoclosed

chore(deps): update node.js to v20 - autoclosed #30

Triggered via pull request August 17, 2023 03:44
Status Success
Total duration 14m 37s
Artifacts 1

go-static-checks.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors
visits the app root url.My First Test visits the app root url: frontend/visits the app root url#L1
The following error originated from your application code, not from Cypress. It was caused by an unhandled promise rejection. > Cannot use 'in' operator to search for 'tunnels' in <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <link rel="icon" href="/favicon.ico"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>AREDN Cloud Node Console</title> <link id="theme-css" rel="stylesheet" type="text/css" href="/themes/mdc-dark-indigo/theme.css"> <script type="module" crossorigin src="/assets/index-6cfb0ab6.js"></script> <link rel="stylesheet" href="/assets/index-e7af3758.css"> </head> <body> <div id="app"></div> </body> </html> When Cypress detects uncaught errors originating from your application it will automatically fail the current test. This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event. https://on.cypress.io/uncaught-exception-from-application
visits the app root url.My First Test visits the app root url: frontend/visits the app root url#L1
The following error originated from your application code, not from Cypress. It was caused by an unhandled promise rejection. > t.data.stats is undefined When Cypress detects uncaught errors originating from your application it will automatically fail the current test. This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event. https://on.cypress.io/uncaught-exception-from-application

Artifacts

Produced during runtime
Name Size
frontend Expired
21.9 MB