-
Notifications
You must be signed in to change notification settings - Fork 30
Description
Hi there, i cant start the hogwarts Demo. I am using mac os.
[email protected] linked ==> /Users/21222433/Documents/TensorFlow_Fed/demo/audio/client/node_modules/federated-learning-client
events.js:167
throw er; // Unhandled 'error' event
^Error: spawn parcel ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:279:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:696:3)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
at onErrorNT (internal/child_process.js:407:16)
[... lines matching original stack trace ...]
at bootstrapNodeJSCore (internal/bootstrap/node.js:696:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
cp: dist/*: No such file or directory
2018-09-12 14:12:26.826263: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.2 AVX AVX2 FMA
(node:10800) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at https://storage.googleapis.com/tfjs-speech-command-model-14w/model.json reason: Unexpected token < in JSON at position 0
at /Users/u719611/Documents/TensorFlow_Fed/demo/audio/server/node_modules/node-fetch/lib/index.js:239:32
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:10800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:10800) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.