Closed nahoskins closed 9 years ago
@nahoskins GitHub API occasionally gives errors on these. Might work after a retry.
There seems to be no https://github.com/noflo/noflo-crypto
@forresto you're right, though there is https://github.com/kenhkan/noflo-crypto
I wonder why this is pulled in as dep
Still no love. Apparently the tech gods frown on me for my component greed.
@nahoskins are you building noflo-ui, or one of the mentioned component libraries?
im rebuilding noflo-ui, on each ammendment to the preview/component.json
strangely, grunt watch does not trigger on writing the changes out of vim.
Warning: failed to fetch https://raw.githubusercontent.com/noflo/noflo-crypto/master/component.json, got 404 "Not Found" Used --force, continuing.
Error: can't find remote for "noflo/noflo-crypto" Warning: failed to fetch https://raw.githubusercontent.com/noflo/noflo-filesystem/master/component.json, got 404 "Not Found" Used --force, continuing. Error: can't find remote for "noflo/noflo-filesystem"
@nahoskins and noflo-ui fails to build to with that error when you have made no modifications? If you need modifications to make the error occur, we'll need to know exactly what they are.
using kenhkan/noflo-crypto DOES solve the symptom.
"kenhkan/noflo-crypto": "*",
"noflo/noflo-filesystem": "*"
Added to the end of deps in preview/component.json
It's trying to find master/component.json and is rather upset when it cannot.
For me, grunt can't find noflo-ui-0.4.0/components/noflo-noflo-strings/graphs/SendJson.fbp
. Restarting npm like 10 times in order to get more than 200 MB of dependencies (wtf) and still missing some is just no fun. This project is ridiciously hard to build.
@wITTus are you building from a git checkout? The dependencies in components/ are not NPM deps, they are component.io deps, which are fetched at grunt build time. component.io has a tendency to get stuck in failing if a download failed once, you may need to do "git clean -dfx" inside components/
@nahoskins Does the crypto problem happens on unmodified noflo-ui build, or only if adding libraries to preview/components.json (if so which)?
@jonnor, I used the 0.4.0 release version.
@wITTus bearing in mind you can always create a runtime with your deps on flowhub, so there is that!
@jonnor the crypto problem only happens after modifying the preview/components.json, although I am currently unaware of any other way of adding components to an unmodified noflo-ui build.
Further, after messing around last night with my own forks, it seems that some of these components are just not set up to work with noflo-ui's "edit preview/component.json" method at all. You can create the component.json file, add an index.js at which point "grunt build" passes all tests, but then the components fail to be implemented.
I need to spend more time familiarising myself with this project because to be frank I don't feel as if I can provide enough help troubleshooting this.
@wiTTUS it builds without problems here, and on Travis CI. You'll have to try the component.io hack mentioned I'm afraid
@nahoskins Yes unfortunately there is not really a better way to manage dependencies in the bundled noflo-browser runtime. Note that this preview/component.json thing is only for NoFlo on browser, not for node.js and other runtimes
@jonnor Ah thank you for the clarification, I was trying to use the UI to do server side work. What is this component.io hack?
@bergie @jonnor @forresto Is there a tested method for installing components for runtimes other than the browser on locally hosted versions of noflo-ui?
@nahoskins for Node.js, you can simply create a local project where you run noflo-nodejs. See the repo for more info: https://github.com/noflo/noflo-nodejs
filesystem, gnome and others return with similar error:
Warning: failed to fetch https://raw.githubusercontent.com/noflo/noflo-crypto/master/component.json, got 404 "Not Found" Use --force to continue.
If these install methods fail there should be documentation to deter users.