Community

Debugging nodejs app.js at 100%

NodeBB Development

Suggested Topics

  • B

    NodeJS 4.0 released

    NodeBB Development
    0 Votes
    17 Posts
    7209 Views
    BriB

    Just a cautionary note, don't try 4.x in prod yet...
    https://github.com/nodejs/node/issues/3370

  • S

    [Best practices?] If I'm running a droplet and want to use multiple urls for different node apps...?

    NodeBB Development
    0 Votes
    4 Posts
    1735 Views
    S

    I restarted nginx, and do so whenever I try to make changes, but it's not working... Is something like this valid? I made sure the file in sites-available and sites-enabled are linked.

    upstream io_nodes { ip_hash; server 127.0.0.1:4567; } server { listen 80; server_name forums.violetcomics.com; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_redirect off; # Socket.io Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; gzip on; gzip_min_length 1000; gzip_proxied off; gzip_types text/plain application/xml application/x-javascript text/css application/json; location @nodebb { proxy_pass http://io_nodes; } location ~ ^/(images|language|sounds|templates|uploads|vendor|src\/modules|nodebb\.min\.js|stylesheet\.css|admin\.css) { root /path/to/nodebb/public/; try_files $uri $uri/ @nodebb; } location / { proxy_pass http://io_nodes; } }

    Edit: Error came back. @_@ I'll get back to it later.

  • K

    Node js process.nextTick doesn't work properly

    NodeBB Development
    0 Votes
    1 Posts
    1609 Views
    K

    Well, I have this issue that I need to do following things:
    1.Mongo Find
    2. Foreach
    3. MongoFind
    4 one more Foreach.

    because of asynchronaus mongo calls it is difficult to get proper result, however process.nextTick should handle this problem and still I have problem:

    function find(dbComm) {

    dbComm.forEach(function (current) { id= parseFloat(current.ID); db.anotherCollection.find({ ID: id}, function (error, result) { result.forEach(function (rank) { if (parseFloat(result.ID) == parseFloat(current.ID)) { rank.rank = 'Some calculations'; } }); }); });

    }

    app.get('/someparams', function (req, res) {

    db.collection.find().sort({ "rank": order }).skip(pagenumber).limit(5, function (err, result) { process.nextTick(function () { find(result, function () { }) }); process.nextTick(function () { res.send(result); }); });

    And on client side I should recive an array where the rank equals 'Some Calculations'
    but unfortunetly it is not...
    However...! If I add setTimeout(function(){}) before res.send(result) (and res.send(result) will be placed inside setTimeout) it actually does work and on client side I recive data with "Some Calculations" but it is just timeout and it fails sometimes and client dont recive "Some Calculations"
    if I put process.nextTick instead of setTimeout it doesnt work and "Some calc..." are not sent.

    Something is beeing done eralier then it should (probably in forEach in find() function)
    and my question is how to deal with it? maybe I should put process.nextTick in different function ?

  • agarcia17A

    Incorporating NodeBB into my web app

    NodeBB Development
    0 Votes
    3 Posts
    1699 Views
    agarcia17A

    @julian thank you! I'll take a look into that plugin 🙂

  • julianJ

    Up and coming js upload library

    NodeBB Development
    0 Votes
    3 Posts
    1207 Views
    julianJ

    Definitely going to keep an eye on this -- it's still fairly new and immature, so we'll see where it goes.

Copyright © 2023 NodeBB | Contributors