These are chat archives for coala/coala-bears
proxywhich has been added into the
check ()function of
safety.py. The commit which adds this argument is https://github.com/pyupio/safety/commit/e0884c2023afa0d0514631011b5e327367d9624c#diff-a0036300f703f514f998583f7758bf19
@refeed , can you finish up coala/coala-bears#1894 ; your commit looks ok, but I cant see the PR. dont stress if the CI is failing - we've got a backlog of red-ness happening
@jayvdb see my comment, https://github.com/coala/coala-bears/issues/1894#issuecomment-460628053
@Naveenaidu do you think we should have gone with ignoring the warning?
No. Ignoring the warning might mean that we really neglect the new errors that might come. That being said, W605 is a pretty important warning since it would be changed into errors in the upcoming versions.
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself. Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-receivedThis randomly appears during my local build process. Restarting the build works. Is this fine?
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received` This randomly appears during my local build process. Restarting the build works. Is this fine?
What do you actually mean by locally? On your branch or Are you running Travis manually via a docker