(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.

[maxbritto]

I am unable to serve my application in development environment since I updated to the latest master this morning.
If I choose the 0.0.42 version it works but not with the master.
Here is the log :

    $ ember serve
    version: 0.0.42-master-d2871b553d
    Livereload server on port 35729
    Serving on http://0.0.0.0:4200
    (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.'
    (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.'
    (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.'
    ...
    -repeating dozens of times-
    ...
    (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.'`

Then nothing happens, no error, nothing. If I try to load the page on chrome I have a timeout after a long time.

If I change the environment to 'production' in .ember-cli then it get served but I really need to use the 'development' environment

[jakecraige]

If you haven't tried already, try rm -rf node_modules && npm cache clear && npm install where you have ember-cli. Also it could be helpful to post the output of ember -v to show your node and npm versions'

I'm not able to recreate this on my machine.

[maxbritto]

Thanks for the help, I did try cleaning up npm and bower but the result is the same.
After I executed your 3 commands I revert to 0.0.42 and so it works. But when I switch to the master release npm link ember-cli the problems comes back.

Here is the result of ember v :

$ ember v
version: 0.0.42-master-d2871b553d
node: 0.10.31
npm: 1.5.0-alpha-4

[stefanpenner]

@maxbritto seems like we have an issue on master, thanks for pointing it out.

[maxbritto]

You're welcome, let me know if I can be of any help.

[bcardarella]

Is there any way to get node give a file/line for the location of that warning?

[rwjblue]

This is generally an issue when a tree depends upon itself, and you end up in a recursive loop.

@maxbritto - Can you please publish a demo repo?

[maxbritto]

I updated this morning to the latest release and I don't have the issue anymore.
I haven't changed my project code, I just updated my ember-cli master :
In my ember-cli folder (outside of my project scope) :

git pull
npm link

In my project

npm link ember-cli

Should I close the issue ?

[rwjblue]

Thanks for following up, glad master is working properly.

[maxbritto]

Sadly I rushed to happiness and now a problem is back. It has been working fine all day and then I ran npm update.
Now the problem is back.
Here is my package.json in case that could help :

{
  "name": "frontoffice",
  "version": "0.0.0",
  "private": true,
  "directories": {
    "doc": "doc",
    "test": "test"
  },
  "scripts": {
    "start": "ember server",
    "build": "ember build",
    "test": "ember test"
  },
  "repository": "https://github.com/stefanpenner/ember-cli",
  "engines": {
    "node": ">= 0.10.0"
  },
  "author": "",
  "license": "MIT",
  "devDependencies": {
    "body-parser": "^1.2.0",
    "broccoli-asset-rev": "0.0.17",
    "broccoli-ember-hbs-template-compiler": "^1.6.1",
    "ember-cli": "0.0.42",
    "ember-cli-ember-data": "0.1.0",
    "ember-cli-inject-live-reload": "^1.0.2",
    "ember-cli-ic-ajax": "0.1.1",
    "ember-cli-qunit": "0.0.7",
    "express": "^4.8.5",
    "broccoli-less-single": "^0.1.4",
    "broccoli-merge-trees": "^0.1.4",
    "broccoli-static-compiler": "^0.1.4",
    "broccoli-unwatched-tree": "^0.1.1",
    "ember-cli-simple-auth": "^0.6.4-1",
    "ember-cli-simple-auth-oauth2": "^0.6.4-1",
    "glob": "^4.0.5"
  }
}

[maxbritto]

I finally managed to get it back working, not really sure how though : i was trying to create a new project with the same issue (which I couldn't) by copying brocfile, packages.json, bower,json, etc.

Here is the list of the commands I used that I think might be the ones which helped :

rm -rf node_modules && npm cache clear && npm install
ember init
npm update npm -g;
npm update -g;

Now I'm back to a working project. If something I did comes back to mind I'll write it here

[stefanpenner]

just a heads-up globally update all npm packages often leads to pain. I wouldn't advise it

[maxbritto]

Noted. Thanks.

[rstudner]

+1 on rm -rf node_modules && npm cache clear && npm install

I had the error and this is what fixed it for me. (in the short term).

I'll dev for a bit and report back if it resurfaces.

[thejchap]

Seems as if this came back on 0.0.46-master-cff6419a5b...rm -rf node_modules && npm cache clear && npm install did not fix. 0.0.46 works fine

[stefanpenner]

@thejchap I wonder if it is a race non-existent pre symlink world. RSVP calls nextTick, but guards against this scenario. I wonder though if we have 2 different versions of RSVP interacting with each other if this may happen. My first thought on the mater says not but i may be surprised.

[thejchap]

@stefanpenner Seems like grabbing the newest RSVP takes care of it...maybe... 👍

#2140

[stefanpenner]

Strange. I don't remember making any related changes, oh well

[rwjblue]

I kinda doubt it is related, but yeah upgrades!