Test app with no changes crashed the server
See original GitHub issueAfter installing hoodie, starting test app and click around a little bit (added a to-do, but no changes to its code), I left my computer open with it and woke up to this server error(s):
[hoodie] Hoodie app is running!
Debug: internal, implementation, error
TypeError: reply(...).code is not a function
at /Users/sergi/programming/testapp/node_modules/hoodie-server/lib/server/plugins/api/index.js:61:20
at finish (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/wreck/lib/index.js:309:16)
at wrapped (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/wreck/node_modules/hoek/lib/index.js:858:20)
at onReaderFinish (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/wreck/lib/index.js:346:16)
at g (events.js:273:16)
at emitNone (events.js:85:20)
at emit (events.js:179:7)
at finishMaybe (_stream_writable.js:478:14)
at endWritable (_stream_writable.js:488:3)
at Writable.end (_stream_writable.js:453:5)
[db_updates] Error: connect ECONNREFUSED 127.0.0.1:6003
[db_updates] Error: connect ECONNREFUSED 127.0.0.1:6003
events.js:130
EventEmitter.prototype.emit = function emit(type) {
^
RangeError: Maximum call stack size exceeded
at Feed.emit (events.js:130:44)
at Domain.<anonymous> (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/couchr/couchr-node.js:263:14)
at emitOne (events.js:90:13)
at Domain.emit (events.js:182:7)
at Feed.emit (events.js:152:14)
at Domain.<anonymous> (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/couchr/couchr-node.js:263:14)
at emitOne (events.js:90:13)
at Domain.emit (events.js:182:7)
at Feed.emit (events.js:152:14)
at Domain.<anonymous> (/Users/sergi/programming/testapp/node_modules/hoodie-server/node_modules/couchr/couchr-node.js:263:14)
I had open both the actual app and the admin panel for it.
OSX
Node version: v5.9.1
NPM version: 3.7.3
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
[nodemon] app crashed - waiting for file changes before ...
I want to it restart automatically after app crashed. I use nodemon in live project. so it is not possible every time to...
Read more >nodemon app crashed - waiting for file changes before starting
This is happening because of all the running server processes in the background. So all you need to do is stop them from...
Read more >NODEMON — app crashed — waiting for file changes before ...
This is a very common error, when you start your server with nodemon, you might face this error. ... "test": "echo \"Error: no...
Read more >"NO_CRASH_STACK + 0" Crash (only on testflight)
When I built an app for Testflight with Xcode 13.1 (App Store version), it crashes on launch when installed from TestFlight, as everyone ......
Read more >Nodemon app crashed - Waiting for file changes before ...
It will fix the "Nodemon app crashed - Waiting for file changes before starting" error issue for sure. Solution2 - Check for any...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey @sergi I think wer resolved the problem meanwhile 😃 If you can still reproduce it, please reopen the issu. Thanks!
here’s our current milestone plan: http://gr2m.github.io/milestones/
use the new one. It might still have a few bugs, but it’s less error prone as we use PouchDB internally now for data persistence and sync. Also the code of the new Hoodie is very hackable. If you run into a problem, you’ll be able to debug it yourself and contribute a fix. We put a lot of efforts to make that as simple as possible.