You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at many of the PRs, they are failing for reasons beyond their changes, suggesting there is a configuration issue with the CI.
What I see in the build logs, as a common failure:
(+) Debug output: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n"
(+) Error: Got an invalid response from Node Security, please email the above debug output to [email protected]
Makefile:9: recipe for target 'security' failed
make: *** [security] Error 1
npm ERR! Test failed. See above for more details.
The command "npm test" exited with 1.
cache.2
store build cache
Doing a quick bit of research suggestion that nodesecurity.io has shut down, leading to this situation:
Looking at many of the PRs, they are failing for reasons beyond their changes, suggesting there is a configuration issue with the CI.
What I see in the build logs, as a common failure:
Doing a quick bit of research suggestion that nodesecurity.io has shut down, leading to this situation:
https://stackoverflow.com/questions/53716991/node-security-service-shutdown-getaddrinfo-enotfound-api-nodesecurity-io
Maybe an opportunity to use Github workflows in place of Travis or to limit the supported NodeJS versions?
The text was updated successfully, but these errors were encountered: