[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/418 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

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 +1 please squash merge. Thanks On Sun, Nov 13, 2016 at 3:57 AM, Omkar wrote: > @lewismc I have replicated the README in the

[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 I have replicated the README in the root directory of climate and added to climate/ocw-ui/frontend. The warning was raised because npm was searching for readme data in ocw-ui. I also

[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 http://stackoverflow.com/questions/18057466/npm-how-to-fix-no-readme-data Please squash your commits if you could as well. Thanks, appreciated. --- If your project is set up

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/418 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

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 Okay on it, Can you let me know what you wanted to add into the READme? I did not get that part. Thanks. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 Thats exactly right. There is nothing we can do about the deprecated transitive dependencies. Please merge in master branch. One thing is that we need to run the tests as well

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 I have a theory that I have learnt from my digging up on this kind of issues, the modules that we are using in turn have unmet dependencies and their respective owners need t update them, I am

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 @jarifibrahim yes exactly, I got the same errors and I mentioned the same earlier, according to my understanding the errors are not caused due to our part of the code, I have updated every

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user jarifibrahim commented on the issue: https://github.com/apache/climate/pull/418 @Omkar20895 `npm install` would create a folder `node_modules` and install all the dependencies in it. If you do `npm install -g` then the dependencies are installed globally. I tried

[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

[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

[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

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user agoodm commented on the issue: https://github.com/apache/climate/pull/418 @Omkar20895 How are you creating the `virtualenv`? The `podaacpy` related errors that are being shown in the CI log output were fixed in 1.6.0 which is now on conda-forge. Are you certain that you

[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 I tried this PR out in a clean virtualenv and I still got the same errors. I think we need to take others opinion if everything is working fine in your system with this PR.

[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 I am on a vacation so I won't be able to do it, I am gonna update this as soon as I return to my university this sunday. Thanks. --- If your project is set up for it, you can reply to

[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 can you delete the node dependencies folder, try again with the fresh PR applied and post your output here? --- If your project is set up for it, you can reply to this email and have

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 I haven't tested the branch yet, I am testing it now. I merged your PR just now into my branch and hence it appeared here. --- If your project is set up for it, you can reply to this email and

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 You've not addressed the README issue in the build. Also can you remove the PO.DAAC stuff? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/418 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

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 Hi @Omkar20895 please merge the following into your remote branch and then test it out. https://github.com/Omkar20895/climate/pull/1 Thanks --- If your project is set up for it, you can

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 Actually, hold off on the merge. This is not right. --- 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

[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 this is looking good. If you could just add the data to the README then I am +1 to merge into master branch. --- If your project is set up for it, you can reply to this email and have

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user lewismc commented on the issue: https://github.com/apache/climate/pull/418 #dynamite --- 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

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user agoodm commented on the issue: https://github.com/apache/climate/pull/418 By the way in regards to the pydap tests failing: this is not on our end, but something the OPeNDAP folks need to fix. I have been in contact with their support team. --- If your project is set up

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user Omkar20895 commented on the issue: https://github.com/apache/climate/pull/418 I don't know how the first commit got in the way here. Anyways just try out the package.json once and I will close this PR. --- If your project is set up for it, you can reply to this email

[GitHub] climate issue #418: CLIMATE-886 Updating front-end dependencies.

Github user OCWJenkins commented on the issue: https://github.com/apache/climate/pull/418 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