[jira] [Commented] (CLIMATE-886) Upgrade Frontend Dependencies
[
https://issues.apache.org/jira/browse/CLIMATE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651546#comment-15651546
]
ASF GitHub Bot commented on CLIMATE-886:
Github user Omkar20895 commented on the issue:
https://github.com/apache/climate/pull/418
@lewismc yes I did. Just to be sure node dependencies is the only folder
that npm install generates right?? If that's right then I did delete that
folder and tried the patch.
> Upgrade Frontend Dependencies
> -
>
> Key: CLIMATE-886
> URL: https://issues.apache.org/jira/browse/CLIMATE-886
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: webapp
>Affects Versions: 1.2.0
>Reporter: Lewis John McGibbney
> Fix For: 1.3.0
>
>
> When I build the frontend code I get the following messy logging. The first
> 20 or so lines indicate deprecated dependency declarations which we should
> fix.
> {code}
> lmcgibbn@LMC-056430 /usr/local/climate/ocw-ui/frontend(master) $ npm install
> npm WARN package.json ocwui@1.1.0 No README data
> npm WARN engine karma@0.12.37: wanted: {"node":">=0.8 <=0.12 || >=1 <=2"}
> (current: {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into
> npm and is now out of date with respect to npm
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained.
> Upgrade to lodash@^4.0.0.
> npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated find-file@0.1.4: Use the globby package instead
> npm WARN deprecated CSSselect@0.4.1: the module is now available as
> 'css-select'
> npm WARN deprecated tough-cookie@0.9.15: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated CSSwhat@0.4.7: the module is now available as 'css-what'
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/tabtab/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated tough-cookie@0.12.1: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> > optipng-bin@0.3.11 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin
> > node index.js
> ✔ pre-build test passed successfully!
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> > gifsicle@0.1.7 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle
> > node index.js
> ✔ pre-build test passed successfully!
> > jpegtran-bin@0.2.8 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> > node index.js
> > pngquant-bin@0.3.5 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin
> > node index.js
> ✔ pre-build test passed successfully!
> -
> > ws@0.4.32 install
> > /usr/local/climate/ocw-ui/frontend/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> > (node-gyp rebuild 2> builderror.log) || (exit 0)
> -
> > yo@1.8.5 postinstall /usr/local/climate/ocw-ui/frontend/node_modules/yo
> > yodoctor
> Yeoman Doctor
> Running sanity checks on your system
> ✔
[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.
Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 @lewismc yes I did. Just to be sure node dependencies is the only folder that npm install generates right?? If that's right then I did delete that folder and tried the patch. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (CLIMATE-886) Upgrade Frontend Dependencies
[
https://issues.apache.org/jira/browse/CLIMATE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651429#comment-15651429
]
ASF GitHub Bot commented on CLIMATE-886:
Github user lewismc commented on the issue:
https://github.com/apache/climate/pull/418
@Omkar20895 have you tried deleting the npm-generated material in the
ocw-ui directory and trying again?
> Upgrade Frontend Dependencies
> -
>
> Key: CLIMATE-886
> URL: https://issues.apache.org/jira/browse/CLIMATE-886
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: webapp
>Affects Versions: 1.2.0
>Reporter: Lewis John McGibbney
> Fix For: 1.3.0
>
>
> When I build the frontend code I get the following messy logging. The first
> 20 or so lines indicate deprecated dependency declarations which we should
> fix.
> {code}
> lmcgibbn@LMC-056430 /usr/local/climate/ocw-ui/frontend(master) $ npm install
> npm WARN package.json ocwui@1.1.0 No README data
> npm WARN engine karma@0.12.37: wanted: {"node":">=0.8 <=0.12 || >=1 <=2"}
> (current: {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into
> npm and is now out of date with respect to npm
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained.
> Upgrade to lodash@^4.0.0.
> npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated find-file@0.1.4: Use the globby package instead
> npm WARN deprecated CSSselect@0.4.1: the module is now available as
> 'css-select'
> npm WARN deprecated tough-cookie@0.9.15: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated CSSwhat@0.4.7: the module is now available as 'css-what'
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/tabtab/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated tough-cookie@0.12.1: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> > optipng-bin@0.3.11 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin
> > node index.js
> ✔ pre-build test passed successfully!
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> > gifsicle@0.1.7 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle
> > node index.js
> ✔ pre-build test passed successfully!
> > jpegtran-bin@0.2.8 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> > node index.js
> > pngquant-bin@0.3.5 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin
> > node index.js
> ✔ pre-build test passed successfully!
> -
> > ws@0.4.32 install
> > /usr/local/climate/ocw-ui/frontend/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> > (node-gyp rebuild 2> builderror.log) || (exit 0)
> -
> > yo@1.8.5 postinstall /usr/local/climate/ocw-ui/frontend/node_modules/yo
> > yodoctor
> Yeoman Doctor
> Running sanity checks on your system
> ✔ Global configuration file is valid
> ✔ NODE_PATH matches the npm root
> ✔
[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.
Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 @Omkar20895 have you tried deleting the npm-generated material in the ocw-ui directory and trying again? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (CLIMATE-890) Changing time format when calendar in the netcdf file is 360_day
[ https://issues.apache.org/jira/browse/CLIMATE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651358#comment-15651358 ] ASF GitHub Bot commented on CLIMATE-890: Github user asfgit closed the pull request at: https://github.com/apache/climate/pull/421 > Changing time format when calendar in the netcdf file is 360_day > > > Key: CLIMATE-890 > URL: https://issues.apache.org/jira/browse/CLIMATE-890 > Project: Apache Open Climate Workbench > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Huikyo Lee >Assignee: Huikyo Lee > > netCDF4.num2date function does generate a list of datetime objects when > calendar is 360_day. utils.decode_time_values will be updated to fix this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLIMATE-890) Changing time format when calendar in the netcdf file is 360_day
[ https://issues.apache.org/jira/browse/CLIMATE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651355#comment-15651355 ] ASF GitHub Bot commented on CLIMATE-890: Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/421 Merged build triggered. Test Failed. > Changing time format when calendar in the netcdf file is 360_day > > > Key: CLIMATE-890 > URL: https://issues.apache.org/jira/browse/CLIMATE-890 > Project: Apache Open Climate Workbench > Issue Type: Improvement >Affects Versions: 1.1.0 >Reporter: Huikyo Lee >Assignee: Huikyo Lee > > netCDF4.num2date function does generate a list of datetime objects when > calendar is 360_day. utils.decode_time_values will be updated to fix this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] climate pull request #421: CLIMATE-890 - Changing time format when calendar ...
Github user asfgit closed the pull request at: https://github.com/apache/climate/pull/421 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] climate issue #421: CLIMATE-890 - Changing time format when calendar in the ...
Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/421 Merged build triggered. Test Failed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (CLIMATE-886) Upgrade Frontend Dependencies
[
https://issues.apache.org/jira/browse/CLIMATE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650578#comment-15650578
]
ASF GitHub Bot commented on CLIMATE-886:
Github user Omkar20895 commented on the issue:
https://github.com/apache/climate/pull/418
@agoodm this is not regarding travis build this is regarding the node
dependencies. Please correct me if I am wrong.
> Upgrade Frontend Dependencies
> -
>
> Key: CLIMATE-886
> URL: https://issues.apache.org/jira/browse/CLIMATE-886
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: webapp
>Affects Versions: 1.2.0
>Reporter: Lewis John McGibbney
> Fix For: 1.3.0
>
>
> When I build the frontend code I get the following messy logging. The first
> 20 or so lines indicate deprecated dependency declarations which we should
> fix.
> {code}
> lmcgibbn@LMC-056430 /usr/local/climate/ocw-ui/frontend(master) $ npm install
> npm WARN package.json ocwui@1.1.0 No README data
> npm WARN engine karma@0.12.37: wanted: {"node":">=0.8 <=0.12 || >=1 <=2"}
> (current: {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into
> npm and is now out of date with respect to npm
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will
> fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as
> possible. Use 'npm ls graceful-fs' to find it in the tree.
> npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained.
> Upgrade to lodash@^4.0.0.
> npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated find-file@0.1.4: Use the globby package instead
> npm WARN deprecated CSSselect@0.4.1: the module is now available as
> 'css-select'
> npm WARN deprecated tough-cookie@0.9.15: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> npm WARN deprecated CSSwhat@0.4.7: the module is now available as 'css-what'
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> > spawn-sync@1.0.15 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/yo/node_modules/tabtab/node_modules/inquirer/node_modules/external-editor/node_modules/spawn-sync
> > node postinstall
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> npm WARN deprecated tough-cookie@0.12.1: ReDoS vulnerability parsing
> Set-Cookie https://nodesecurity.io/advisories/130
> > optipng-bin@0.3.11 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin
> > node index.js
> ✔ pre-build test passed successfully!
> npm WARN engine punycode@2.0.1: wanted: {"node":">=6"} (current:
> {"node":"4.5.0","npm":"2.15.9"})
> > gifsicle@0.1.7 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle
> > node index.js
> ✔ pre-build test passed successfully!
> > jpegtran-bin@0.2.8 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> > node index.js
> > pngquant-bin@0.3.5 postinstall
> > /usr/local/climate/ocw-ui/frontend/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin
> > node index.js
> ✔ pre-build test passed successfully!
> -
> > ws@0.4.32 install
> > /usr/local/climate/ocw-ui/frontend/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> > (node-gyp rebuild 2> builderror.log) || (exit 0)
> -
> > yo@1.8.5 postinstall /usr/local/climate/ocw-ui/frontend/node_modules/yo
> > yodoctor
> Yeoman Doctor
> Running sanity checks on your system
> ✔ Global configuration file is valid
> ✔ NODE_PATH matches
[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.
Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 @agoodm this is not regarding travis build this is regarding the node dependencies. Please correct me if I am wrong. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
