sgress454

Fix failing tests from a CI run. The argument is a GitHub Actions run URL or run ID: $ARGUMENTS

Step 1: Identify failing jobs

Extract the run ID from the URL (the numeric path segment after /runs/). Use gh run view <run_id> to list the jobs, then find the failing ones:

gh run view <run_id> --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name: .name, id: .databaseId}'

sgress454

[
  {
    "with": [
      {
        "name": {
          "type": "default",
          "value": "extension_safety_hub_menu_notifications"
        },
        "stmt": {
          "tableList": [

sgress454

#!/Users/scottmac/.nvm/v6.3.0/bin/node

/**
 * Pre-commit hook to prevent commits that change models unless they
 * also include a migration file.
 *
 * To skip, use the `--no-verify` option when committing.
 * (useful if you just added a comment to a model)
 */

sgress454

Reference: https://gitter.im/balderdashy/sails?at=58be4b1af1a33b62758d57ea

Is there anyway that I can add a method to all routes?

The issue

Given a Sails app with two models User and Pet, how do we create a single controller action foo and have it automatically run on requests for both /user/foo and /pet/foo?

The solution

sgress454

Given the appropriate columnType, MySQL and PostgreSQL will handle storing buffers for you.

Model

module.exports = {
  attributes: {
    name: {
      type: 'string',
 },

sgress454

Dependencies removed in Sails v1.0

Dependency	Version
anchor	~0.10.5
connect-flash	0.1.1
ejs-locals	1.0.2
express-handlebars	3.0.0
grunt	1.0.1
grunt-cli	1.2.0

sgress454

An algorithm for ordering routes

Definition of a "route"

For the purposes of this algorithm, a route is a string containing:

• An optional HTTP verb (or ALL) prefix, followed by a space, followed by:
• 1 or more path components, where each path component is:
  • A forward slash /, followed by:
• A colon : followed by any combination of letters and numbers (a "param"), OR

sgress454

The instructions below will work with the regular Git command-line tool or the hub CLI tool (makes things a bit faster).

# Make a new Sails app with a descriptive title
sails new waterline-issue-cant-create-records
cd waterline-issue-cant-create-records

# Install the minimum node modules needed to reproduce the issue, making careful note of versions
# and remembering to use --save
npm install sails-mysql --save

sgress454

The instructions below will work with the regular Git command-line tool or the hub CLI tool (makes things a bit faster).

# Make a new Sails app with a descriptive title
sails new sails-issue-cant-use-handlebars-layout
cd sails-issue-cant-use-handlebars-layout

# Install the minimum node modules needed to reproduce the issue, making careful note of versions
# and remembering to use --save and --save-exact
npm install handlebars@4.0.5 --save --save-exact

sgress454

├── bcrypt@0.8.5 extraneous
├── bcryptjs@2.3.0
├─┬ connect-redis@1.4.5
│ ├─┬ debug@2.2.0
│ │ └── ms@0.7.1
│ └── redis@0.7.3
├── ejs@0.8.8 -> /home/ubuntu/.nvm/versions/node/v4.2.1/lib/node_modules/sails/node_modules/ejs
├── forever@0.15.1 extraneous
├─┬ grunt@0.4.2 -> /home/ubuntu/.nvm/versions/node/v4.2.1/lib/node_modules/sails/node_modules/grunt