Update:

Sails v0.10.0-rc3 is now available on npm.

Upgrading to Sails v0.10 beta:

Install: $ sudo npm install -g sails@beta -g

Docs: beta.sailsjs.org

Also see: https://github.com/balderdashy/waterline-docs

Migration Guide for v0.9.x apps: https://github.com/balderdashy/sails-docs/blob/master/Migration-Guide.md

We're working on improving docs in general, but we could really use your help- please feel free to submit pull requests to https://github.com/balderdashy/sails-docs. The changes go live to beta.sailsjs.org (and eventually sailsjs.org proper, when we set the latest tag on v0.10)

I'm on Sails 0.10. I have a Model which has a collection of Model which in turn has more Model. I know how to populate the first child but how do I recursively populate the rest of the children?

Hey, All the cool guys are moving to gulp :)

Few reasons to consider gulp vs grunt:

1. i've used it and absolutely love it
2. uses stream and code vs configuration approach, which makes the code much more readable
3. task dependency done correctly
4. faster

I've run a few tests on some of my projects and the results are really great. lines of code reduced and the all this grunt config(ala xml but in json) is gone.

what do you think?

It would be nice to be able to specify custom indexes. so for example index: "customIndex" the string customIndex would get passed along to the adapter.

If the index was a bool then the current behavior would hold.

I have created a new sails js app and did not change any code in it.

Than I used pm2 to launch two instance of that app. Memory keep increasing without hitting app even once.

I have done the same with basic express.js app with following code but it does not increase memory

" var express = require('express'); var app = express();

app.get('/', function (req, res) { res.send('Hello World!'); });

var server = app.listen(3000, function () { var host = server.address().address; var port = server.address().port;

console.log('Example app listening at http://%s:%s', host, port); }); "

If an object has an associated collection, it is not clear how (or even if its possible) to query into that associated object stuff.

Pet has an Owner Owner has an emailAddress

How do I select all of the Pets whose owner has an emailAddress == "[email protected]"

While its easy to do 2 queries to accomplish this:

1. Find the owner who has an emailAddress == "[email protected]" and get that persons id
2. Find all Pets who have the id from query 1

It seems that there would be a better syntax for this:

Pet.findAll({ "owner.emailAddress" : "[email protected]" })

Now whether or not this is internally optimized or just syntactic sugar doesn't matter, its much easier to read and write.

Further, if a Pet has a breed how would I select the email addresses of all of the owners whose Pet.breed == "beagle"

Owner.findAll({"pet.breed" : "beagle"})

The select is being ignored.. getting back the full records instead of just the titles.

Model.find().populate(assoc.alias, { select: ['title']});

Not sure if its only on mongo?

UPDATE @dmarcelino: changed this issue into a feature request.

Running Sails v0.11.0 and Node v0.12.0

When I run

sails new app; cd app
sails debug

Console logs...

error: Grunt :: Error: listen EADDRINUSE
    at exports._errnoException (util.js:746:11)
    at Agent.Server._listen2 (net.js:1129:14)
    at listen (net.js:1155:10)
    at Agent.Server.listen (net.js:1240:5)
    at Object.start (_debugger_agent.js:20:9)
    at startup (node.js:86:9)
    at node.js:814:3

No conflicting ports were listening prior to running sails. Looking at travis.yml is only node v0.10.x supported currently?

Add Swagger to AUTO document the API in any project: https://developers.helloreverb.com/swagger/

It would go well with the overall Sails mentality.

sample in use here: http://swagger.wordnik.com/#!/pet

Problem occurs on Win7 with sails.js 0.9.7 (0.9.4 is working fine). Node version is 0.10.20.

steps to reproduce:

npm install -g sails
sails new app
cd app
sails lift

if you visit http://localhost:1337/ you will get the following error:

{
  "status": 500,
  "errors": [
    "Failed to lookup view \"home/index\""
  ]
}

can someone confirm that?

I'm trying to use Skipper to save uploaded images, but it's only working on some files. Some files finish, and successfully write to the disk. Some files finish uploading, but the file that's written is empty, and some files just hang on uploading until it times out. When it cancels or hangs, it's on the same file, so it isn't randomly not working.

I found two working and non-working files to log the callback, and this is what it said (these weren't uploaded all at once, and the working-not-working pattern isn't a coincidence)

[ { size: 2005363,
    type: 'image/jpeg',
    filename: 'Success-1.jpg',
    status: 'bufferingOrWriting',
    field: 'avatarUpload',
    extra: undefined } ]
[ { size: 251156,
    type: 'image/jpeg',
    filename: 'Cancelled-1.jpg',
    status: 'cancelled',
    field: 'avatarUpload',
    extra: undefined } ]
[ { size: 2337904,
    type: 'image/jpeg',
    filename: 'Success-2.jpg',
    status: 'bufferingOrWriting',
    field: 'avatarUpload',
    extra: undefined } ]
[ { size: 329172,
    type: 'image/jpeg',
    filename: 'Cancelled-2.jpg',
    status: 'cancelled',
    field: 'avatarUpload',
    extra: undefined } ]

It's also probably worth saying that if I don't comment out stream.pause() on line 33 of node_modules/skipper/node_modules/connect/node_modules/raw-data/index.js that I get this error.

Error: Cannot switch to old mode now.
    at emitDataEvents (_stream_readable.js:730:11)
    at IncomingMessage.Readable.pause (_stream_readable.js:721:3)
    at module.exports (/Users/Nate/Desktop/Projects/Active/project/node_modules/skipper/node_modules/connect/node_modules/raw-body/index.js:33:14)
    at json (/Users/Nate/Desktop/Projects/Active/project/node_modules/skipper/node_modules/connect/lib/middleware/json.js:51:5)
    at _parseHTTPBody (/Users/Nate/Desktop/Projects/Active/project/node_modules/skipper/index.js:71:5)
    at Object.retryBodyParser [as handle] (/Users/Nate/Desktop/Projects/Active/project/node_modules/sails/lib/express/bodyParserRetry.js:36:36)
    at next (/Users/Nate/Desktop/Projects/Active/project/node_modules/sails/node_modules/express/node_modules/connect/lib/proto.js:190:15)
    at next (/Users/Nate/Desktop/Projects/Active/project/node_modules/sails/node_modules/express/node_modules/connect/lib/proto.js:192:9)
    at Parser.next (/Users/Nate/Desktop/Projects/project/node_modules/skipper/index.js:97:20)
    at passControlToApp (/Users/Nate/Desktop/Projects/Active/project/node_modules/skipper/lib/Parser/parse.js:172:11)
    at null._onTimeout (/Users/Nate/Desktop/Projects/Active/project/node_modules/skipper/node_modules/async/lib/async.js:668:17)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

This only happens on the files that would otherwise be successful. If I upload one that'll be blank, then it works, but still writes an empty file.

I'm using Skipper 0.1.6 with Sails 0.9.8. But I've tried with Sails 0.9.16, with the same results

Node version: v18.12.1 Sails version (sails): 1.5.3

Hi there! currently express 4.17.1 is used in sails. However there is a severe vulnerability in one of the dependencies (qs), which allows prototype pollution by placing an attack payload in the query string. For more details see this advisory: https://github.com/advisories/GHSA-hrpp-h998-j3pp Express has updated the dependencies to a non-vulnerable version with 4.17.3

Would it be possible to update the express dependency in sails to 4.17.3?

Node version: 16.18.1 Sails version (sails): 1.5.2 ORM hook version (sails-hook-orm): 4.0.1 Sockets hook version (sails-hook-sockets): 2.0.1 Organics hook version (sails-hook-organics): N/A Grunt hook version (sails-hook-grunt): 5.0.0 Uploads hook version (sails-hook-uploads): N/A DB adapter & version (e.g. [email protected]): [email protected] Skipper adapter & version (e.g. [email protected]): N/A

I received the below error message:

You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
AdapterError: Unexpected error from database adapter: not master and slaveOk=false
    at Deferred._.extend._WLModel [as _handleExec] (/home/usera/service-a/source/node_modules/waterline/lib/waterline/methods/update-one.js:161:15)
    at Deferred.exec (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:286:10)
    at Deferred.tryCatcher (/home/usera/service-a/source/node_modules/bluebird/js/release/util.js:11:23)
    at ret (eval at makeNodePromisifiedEval (/home/usera/service-a/source/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:14:23)
    at Deferred.toPromise (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:572:19)
    at Deferred.then (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:431:22)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
AdapterError: Unexpected error from database adapter: Primary stepped down while waiting for replication
    at _afterCounting (/home/usera/service-a/source/node_modules/waterline/lib/waterline/methods/update-one.js:191:17)
    at _afterTalkingToAdapter (/home/usera/service-a/source/node_modules/waterline/lib/waterline/methods/count.js:227:16)
    at Object.success (/home/usera/service-a/source/node_modules/sails-mongo/lib/private/do-with-connection.js:254:18)
    at /home/usera/service-a/source/node_modules/machine/lib/private/help-build-machine.js:1517:30
    at proceedToFinalAfterExecLC (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:1185:16)
    at proceedToInterceptsAndChecks (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:913:12)
    at proceedToAfterExecSpinlocks (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:845:10)
    at /home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:303:7
    at /home/usera/service-a/source/node_modules/machine/lib/private/help-build-machine.js:954:24
    at Function.handlerCbs.success (/home/usera/service-a/source/node_modules/machine/lib/private/help-build-machine.js:814:26)
    at Object.fn (/home/usera/service-a/source/node_modules/sails-mongo/lib/private/machines/release-connection.js:77:18)
    at wrapper (/home/usera/service-a/source/node_modules/@sailshq/lodash/lib/index.js:3282:19)
    at Deferred.parley.retry [as _handleExec] (/home/usera/service-a/source/node_modules/machine/lib/private/help-build-machine.js:1076:19)
    at Deferred.exec (/home/usera/service-a/source/node_modules/parley/lib/private/Deferred.js:286:10)
    at Deferred.switch (/home/usera/service-a/source/node_modules/machine/lib/private/help-build-machine.js:1469:16)
    at /home/usera/service-a/source/node_modules/sails-mongo/lib/private/do-with-connection.js:242:92

Waterline or sails-mongo seems not to catch this exception. So I should wait timeout in this request. Could you fix it, please?

Currently, latest version in npm is v1.5.3. But CHANGELOG.md and Releases in this GitHub are not latest.

I use sails in my production application. I would like to know latest version is safe to upgrade in my environment, however I cannot find the information

When sending a large string to controller, in req.body I find an array, so this string is divided on many parts. String length is 10700 characters.

Node version: 16.15.1 Sails version (sails): 1.5.2 ORM hook version (sails-hook-orm): 3.0.2 Sockets hook version (sails-hook-sockets): 2.0.0 Grunt hook version (sails-hook-grunt): 1.0.4 Skipper version (e.g. [email protected]): 0.9.1

Node version: v14.17.6 Sails version (sails): 1.5.3 ORM hook version (sails-hook-orm): 3.0.2 Sockets hook version (sails-hook-sockets): N/A Organics hook version (sails-hook-organics): N/A Grunt hook version (sails-hook-grunt): 5.0.0 Uploads hook version (sails-hook-uploads): N/A DB adapter & version (e.g. [email protected]): sails-postgresql 2.0.0 Skipper adapter & version (e.g. [email protected]): 0.9.1

In order to make a sails API available to be called from specific external hosts, cors issue was raised. After apply configs as described in documentation:

module.exports.security = {
  csrf: true,
  cors: {
    allRoutes: true,
    allowOrigins:
      [
        "https://url1",
        "http://url2",
        "https://url3"
      ],
    allowCredentials: true,
    allowRequestHeaders: "Origin, Content-Type, x-xsrf-token",
  }
};

It was noticed a strange behaviour.. locally it works as expected, but when deployed to server with kubernetes the behaviour is the opposite! for requests that should be allowed CORS error is raised, for requests that should be NOT allowed successful answers are returned.

ps: trying to use also CSRF token to help in CORS issue but with no success

it seems the header Access-Control-Allow-Origin is overriden, then in the request there are 2 Access-Control-Allow-Origin

--> following the debug it seems the requests are blocked in route middleware.. but we can't debug what happens there and why this overwrite happens..

Can you help here?