| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| ret.stderr.indexOf('DEPRECATION:') < 0; | ||
| if (ret.error || (ret.stderr.length != 0 && isNotPipWarning)) { | ||
| this.log('Unhandled error in pip, not deploying to AWS.'); | ||
| return BbPromise.reject(ret.error) |
There was a problem hiding this comment.
One could consider to change the reject message for errors that is not a warning (undefined when from ret.stderr) .
return BbPromise.reject(ret.error || ret.stderr.toString())
Sorry, something went wrong.
There was a problem hiding this comment.
Ah, I briefly searched for how to differentiate errors from warnings in node.js but couldn't find the solution.
I guess it would be even better to not do the rejection for warnings at all?
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes error caused by new python 2.7 deprecation warning.