Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MNIST.ipynb example breaks after first epoch #2

Closed
maxpumperla opened this issue Jan 6, 2016 · 4 comments
Closed

MNIST.ipynb example breaks after first epoch #2

maxpumperla opened this issue Jan 6, 2016 · 4 comments

Comments

@maxpumperla
Copy link

Hi Eder, amazing project, really like where you are going with this. Thanks for putting in the work.

When I run the example provided in MNIST.ipynb, following the installation instructions as provided, on OSX 10.10.4, I get the following error after the first epoch:

 /my/path/agnez_app/node_modules/feathers/node_modules/feathers-commons/lib/sockets/helpers.js:61
            socket[info.method](eventName, dispatchData);
                               ^
TypeError: undefined is not a function
  at /my/path/agnez_app/node_modules/feathers/node_modules/feathers-commons/lib/sockets/helpers.js:61:32
  at Object.defaultDispatcher (/my/path/agnez_app/node_modules/feathers/node_modules/feathers-commons/lib/sockets/helpers.js:39:3)
  at /my/path/agnez_app/node_modules/feathers/node_modules/feathers-commons/lib/sockets/helpers.js:56:20
  at Array.forEach (native)
  at Object.<anonymous> (/my/path/agnez_app/node_modules/feathers/node_modules/feathers-commons/lib/sockets/helpers.js:55:35)
  at emitTwo (events.js:87:13)
  at Object.emit (events.js:169:7)
  at /my/path/agnez_app/node_modules/feathers/lib/mixins/event.js:49:21
  at Array.forEach (native)
  at EventEmitter.<anonymous> (/my/path/agnez_app/node_modules/feathers/lib/mixins/event.js:48:16)
  at emitMany (events.js:108:13)
  at EventEmitter.emit (events.js:179:7)
  at Object.exports.emitEvents (/my/path/agnez_app/node_modules/feathers/node_modules/rubberduck/lib/utils.js:32:18)
  at callbackWrapper (/my/path/agnez_app/node_modules/feathers/node_modules/rubberduck/lib/rubberduck.js:56:15)
  at /my/path/agnez_app/node_modules/feathers-nedb/lib/index.js:137:5
  at callback (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/lib/executor.js:30:17)
  at Cursor.execFn (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/lib/datastore.js:462:14)
  at Cursor._exec (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/lib/cursor.js:172:17)
  at /my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/lib/executor.js:40:13
  at Object.q.process (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/node_modules/async/lib/async.js:731:21)
  at next (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/node_modules/async/lib/async.js:728:27)
  at Immediate._onImmediate (/my/path/agnez_app/node_modules/feathers-nedb/node_modules/nedb/node_modules/async/lib/async.js:24:16)
  at processImmediate [as _immediateCallback] (timers.js:368:17)

Any idea how this comes about? Thanks.

@maxpumperla
Copy link
Author

I should also mention that I noticed mpld3 is missing in requirements.txt and installing coffee script via npm in the Makefile could be a valuable addition.

@EderSantana
Copy link
Member

Hi @maxpumperla! Thanks for the interest in Agnez and suggestions.

I honestly don't understand this error. It should be something with the feathers-client package.
Would you mind asking here: https://github.com/feathersjs/feathers?

@daffl if you have time, can you give us your opinion? This is the deep learning visualization app using feathers I mentioned on twitter.

@daffl
Copy link

daffl commented Jan 15, 2016

Oh cool, I have to check it out! The error is probably due to feathersjs-ecosystem/commons#10. There was a change in a Socket.io minor release that broke Feathers. Upgrading to Feathers 1.3 (ideally with clearing your NPM cache just to be sure to get all the newest dependencies) should fix it (1.3 is fully backwards compatible with any 1.x release).

@maxpumperla
Copy link
Author

Eder, I finally got around to trying this - and it works. Thanks again! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants