Unable to install on Windows 10

I've tried to get this running using the default development configuration on 3 different windows 10 machines without success.
Here are the steps I am taking:

Update Docker to latest version (currently version 17.06.0-ce, build 02c1d87)
Clone and run docker-compose up as instructed

git clone https://github.com/kriasoft/nodejs-api-starter.git example-api
cd example-api                  # Change current directory to the newly created one
docker-compose up               # Launch Docker containers with the Node.js API app running inside

Try to seed databases in spite of error from above step.
winpty docker-compose exec api yarn db-seed

Notice more errors. Try the process again by executing docker-compose down followed by docker-compose up

Below is the output from steps 2-4.
$ docker-compose up
Creating network "exampleapi_default" with the default driver
Creating volume "exampleapi_redis" with default driver
Creating volume "exampleapi_db" with default driver
Creating volume "exampleapi_yarn" with default driver
Pulling redis (redis:4.0.1-alpine)...
4.0.1-alpine: Pulling from library/redis
Digest: sha256:e633cded055a94202e4ccccb8125b7f383cd6ee56527ab890db643383a2647dd
Status: Downloaded newer image for redis:4.0.1-alpine
Pulling db (postgres:9.6.4-alpine)...
9.6.4-alpine: Pulling from library/postgres
Digest: sha256:5fd73de311d304caeb4f907d4f559d322805abc622e4baf5788c6a079ee5224e
Status: Downloaded newer image for postgres:9.6.4-alpine
Pulling api (node:8.3.0-alpine)...
8.3.0-alpine: Pulling from library/node
Digest: sha256:811180c902c56e594832bc553bfc5ba8315959a55d453e045bfe77af9b2341cb
Status: Downloaded newer image for node:8.3.0-alpine
Pulling nginx (nginx:1.13.3-alpine)...
1.13.3-alpine: Pulling from library/nginx
Digest: sha256:24a27241f0450b465f9e9deb30628c524aa81a1aa6936daa41ef7c4345515272
Status: Downloaded newer image for nginx:1.13.3-alpine
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_db_1
Creating exampleapi_db_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_redis_1, exampleapi_db_1, exampleapi_api_1, exampleapi_n                                                                                ginx_1
redis_1  | 1:C 16 Aug 15:41:22.078 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0                                                                                Oo
redis_1  | 1:C 16 Aug 15:41:22.079 # Redis version=4.0.1, bits=64, commit=000000                                                                                00, modified=0, pid=1, just started
db_1     | The files belonging to this database system will be owned by user "po                                                                                stgres".
redis_1  | 1:C 16 Aug 15:41:22.079 # Warning: no config file specified, using th                                                                                e default config. In order to specify a config file use redis-server /path/to/re                                                                                dis.conf
db_1     | This user must also own the server process.
api_1    | yarn install v0.27.5
db_1     |
redis_1  | 1:M 16 Aug 15:41:22.080 * Running mode=standalone, port=6379.
db_1     | The database cluster will be initialized with locale "en_US.utf8".
api_1    | [1/4] Resolving packages...
redis_1  | 1:M 16 Aug 15:41:22.080 # WARNING: The TCP backlog setting of 511 can                                                                                not be enforced because /proc/sys/net/core/somaxconn is set to the lower value o                                                                                f 128.
db_1     | The default database encoding has accordingly been set to "UTF8".
redis_1  | 1:M 16 Aug 15:41:22.080 # Server initialized
api_1    | [2/4] Fetching packages...
db_1     | The default text search configuration will be set to "english".
redis_1  | 1:M 16 Aug 15:41:22.080 # WARNING you have Transparent Huge Pages (TH                                                                                P) support enabled in your kernel. This will create latency and memory usage iss                                                                                ues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/t                                                                                ransparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order                                                                                to retain the setting after a reboot. Redis must be restarted after THP is disab                                                                                led.
db_1     |
redis_1  | 1:M 16 Aug 15:41:22.080 * Ready to accept connections
db_1     | Data page checksums are disabled.
db_1     |
db_1     | fixing permissions on existing directory /var/lib/postgresql/data ...                                                                                ok
db_1     | creating subdirectories ... ok
db_1     | selecting default max_connections ... 100
db_1     | selecting default shared_buffers ... 128MB
db_1     | selecting dynamic shared memory implementation ... posix
db_1     | creating configuration files ... ok
db_1     | running bootstrap script ... ok
db_1     | performing post-bootstrap initialization ... No usable system locales                                                                                were found.
db_1     | Use the option "--debug" to see details.
db_1     | sh: locale: not found
db_1     | ok
db_1     | syncing data to disk ...
db_1     | WARNING: enabling "trust" authentication for local connections
db_1     | You can change this by editing pg_hba.conf or using the option -A, or
db_1     | --auth-local and --auth-host, the next time you run initdb.
db_1     | ok
db_1     |
db_1     | Success. You can now start the database server using:
db_1     |
db_1     |     pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1     |
db_1     | ****************************************************
db_1     | WARNING: No password has been set for the database.
db_1     |          This will allow anyone with access to the
db_1     |          Postgres port to access your database. In
db_1     |          Docker's default configuration, this is
db_1     |          effectively any other container on the same
db_1     |          system.
db_1     |
db_1     |          Use "-e POSTGRES_PASSWORD=password" to set
db_1     |          it in "docker run".
db_1     | ****************************************************
db_1     | waiting for server to start....LOG:  could not bind IPv6 socket: Addr                                                                                ess not available
db_1     | HINT:  Is another postmaster already running on port 5432? If not, wa                                                                                it a few seconds and retry.
db_1     | LOG:  database system was shut down at 2017-08-16 15:42:02 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
db_1     |  done
db_1     | server started
db_1     | ALTER ROLE
db_1     |
db_1     |
db_1     | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initd                                                                                b.d/initdb.sh
db_1     | /docker-entrypoint-initdb.d/initdb.sh: line 2: $'\r': command not fou                                                                                nd
exampleapi_db_1 exited with code 127
api_1    | warning<EMAIL_ADDRESS>The platform "linux" is incompatible with thi                                                                                s module.
api_1    | info<EMAIL_ADDRESS>is an optional dependency and failed compatibil                                                                                ity check. Excluding it from installation.
api_1    | [3/4] Linking dependencies...
api_1    | [4/4] Building fresh packages...
api_1    | Done in 55.49s.
api_1    | Starting 'run'...
api_1    | Starting 'db-migrate'...
api_1    | Error: getaddrinfo EAI_AGAIN db:5432
api_1    |     at Object._errnoException (util.js:1022:11)
api_1    |     at errnoException (dns.js:58:15)
api_1    |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:95:26)
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1010ms
api_1    | Node.js API server is listening on http://api:8080/

$ winpty docker-compose exec api yarn db-seed
yarn db-seed v0.27.5
$ node tools/db.js seed
Starting 'db-seed'...
Error: getaddrinfo EAI_AGAIN db:5432
at Object._errnoException (util.js:1022:11)
at errnoException (dns.js:58:15)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:95:26)
Done in 26.30s.

$ docker-compose down
Stopping exampleapi_nginx_1 ...
Stopping exampleapi_nginx_1 ... done
Stopping exampleapi_api_1 ... done
exampleapi_nginx_1 exited with code 0
exampleapi_api_1 exited with code 0
redis_1  | 1:signal-handler<PHONE_NUMBER>) Received SIGTERM scheduling shutdown...
redis_1  | 1:M 16 Aug 15:48:07.046 # User requested shutdown...
redis_1  | 1:M 16 Aug 15:48:07.046 * Saving the final RDB snapshot before exiting.
redis_1  | 1:M 16 Aug 15:48:07.074 * DB saved on disk
Stopping exampleapi_redis_1 ... done
exampleapi_redis_1 exited with code 0
Removing exampleapi_nginx_1 ... done
Removing exampleapi_api_1 ... done
Removing exampleapi_db_1 ... done
Removing exampleapi_redis_1 ... done
Removing network exampleapi_default

$ docker-compose up
Creating network "exampleapi_default" with the default driver
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_db_1
Creating exampleapi_redis_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_db_1, exampleapi_redis_1, exampleapi_api_1, exampleapi_nginx_1
db_1     | LOG:  database system was interrupted; last known up at 2017-08-16 15:42:07 UTC
db_1     | LOG:  database system was not properly shut down; automatic recovery in progress
db_1     | LOG:  redo starts at 0/14EDC10
redis_1  | 1:C 16 Aug 15:48:31.164 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
db_1     | LOG:  invalid record length at 0/14EDDF0: wanted 24, got 0
redis_1  | 1:C 16 Aug 15:48:31.164 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
db_1     | LOG:  redo done at 0/14EDDC8
redis_1  | 1:C 16 Aug 15:48:31.164 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | LOG:  last completed transaction was at log time 2017-08-16 15:42:07.984983+00
redis_1  | 1:M 16 Aug 15:48:31.166 * Running mode=standalone, port=6379.
db_1     | LOG:  MultiXact member wraparound protections are now enabled
redis_1  | 1:M 16 Aug 15:48:31.166 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     | LOG:  database system is ready to accept connections
redis_1  | 1:M 16 Aug 15:48:31.166 # Server initialized
redis_1  | 1:M 16 Aug 15:48:31.166 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
db_1     | LOG:  autovacuum launcher started
redis_1  | 1:M 16 Aug 15:48:31.166 * DB loaded from disk: 0.000 seconds
redis_1  | 1:M 16 Aug 15:48:31.166 * Ready to accept connections
api_1    | Starting 'run'...
api_1    | Starting 'db-migrate'...
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
api_1    | error: database "dev" does not exist
api_1    |     at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:546:11)
api_1    |     at Connection.parseMessage (/usr/src/app/node_modules/pg/lib/connection.js:371:19)
api_1    |     at Socket. (/usr/src/app/node_modules/pg/lib/connection.js:114:22)
api_1    |     at emitOne (events.js:115:13)
api_1    |     at Socket.emit (events.js:210:7)
api_1    |     at addChunk (_stream_readable.js:252:12)
api_1    |     at readableAddChunk (_stream_readable.js:239:11)
api_1    |     at Socket.Readable.push (_stream_readable.js:197:10)
api_1    |     at TCP.onread (net.js:589:20)
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1146ms
api_1    | Node.js API server is listening on http://api:8080/
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist

@MikePugs try setting CHOKIDAR_USEPOLLING environment variable in your docker-compose-override.yml to true (or 1)

No luck.
My Steps:

Created the following docker-compose.override.yml:

version: '3'

services:
  api:
    environment:
      - CHOKIDAR_USEPOLLING=true

Removed all existing containers

Ran docker-compose up

$ docker-compose up
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_redis_1
Creating exampleapi_redis_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_db_1, exampleapi_redis_1, exampleapi_api_1, exampleapi_nginx_1
db_1     | LOG:  database system was interrupted; last known up at 2017-08-16 17:51:18 UTC
db_1     | LOG:  database system was not properly shut down; automatic recovery in progress
redis_1  | 1:C 16 Aug 17:54:48.982 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
db_1     | LOG:  invalid record length at 0/14EE0A8: wanted 24, got 0
redis_1  | 1:C 16 Aug 17:54:48.982 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
db_1     | LOG:  redo is not required
redis_1  | 1:C 16 Aug 17:54:48.982 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | LOG:  MultiXact member wraparound protections are now enabled
redis_1  | 1:M 16 Aug 17:54:48.983 * Running mode=standalone, port=6379.
db_1     | LOG:  database system is ready to accept connections
redis_1  | 1:M 16 Aug 17:54:48.983 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     | LOG:  autovacuum launcher started
redis_1  | 1:M 16 Aug 17:54:48.983 # Server initialized
redis_1  | 1:M 16 Aug 17:54:48.983 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1  | 1:M 16 Aug 17:54:48.983 * DB loaded from disk: 0.000 seconds
redis_1  | 1:M 16 Aug 17:54:48.984 * Ready to accept connections
api_1    | Starting 'run'...
api_1    | Starting 'db-migrate'...
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
api_1    | error: database "dev" does not exist
api_1    |     at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:546:11)
api_1    |     at Connection.parseMessage (/usr/src/app/node_modules/pg/lib/connection.js:371:19)
api_1    |     at Socket. (/usr/src/app/node_modules/pg/lib/connection.js:114:22)
api_1    |     at emitOne (events.js:115:13)
api_1    |     at Socket.emit (events.js:210:7)
api_1    |     at addChunk (_stream_readable.js:252:12)
api_1    |     at readableAddChunk (_stream_readable.js:239:11)
api_1    |     at Socket.Readable.push (_stream_readable.js:197:10)
api_1    |     at TCP.onread (net.js:589:20)
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1012ms
api_1    | Node.js API server is listening on http://api:8080/
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist

No luck.
My Steps:

Created the following docker-compose.override.yml:

version: '3'

services:
  api:
    environment:
      - CHOKIDAR_USEPOLLING=true

Removed all existing containers

Ran docker-compose up

$ docker-compose up
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_redis_1
Creating exampleapi_redis_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_db_1, exampleapi_redis_1, exampleapi_api_1, exampleapi_nginx_1
db_1     | LOG:  database system was interrupted; last known up at 2017-08-16 17:51:18 UTC
db_1     | LOG:  database system was not properly shut down; automatic recovery in progress
redis_1  | 1:C 16 Aug 17:54:48.982 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
db_1     | LOG:  invalid record length at 0/14EE0A8: wanted 24, got 0
redis_1  | 1:C 16 Aug 17:54:48.982 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
db_1     | LOG:  redo is not required
redis_1  | 1:C 16 Aug 17:54:48.982 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | LOG:  MultiXact member wraparound protections are now enabled
redis_1  | 1:M 16 Aug 17:54:48.983 * Running mode=standalone, port=6379.
db_1     | LOG:  database system is ready to accept connections
redis_1  | 1:M 16 Aug 17:54:48.983 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     | LOG:  autovacuum launcher started
redis_1  | 1:M 16 Aug 17:54:48.983 # Server initialized
redis_1  | 1:M 16 Aug 17:54:48.983 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1  | 1:M 16 Aug 17:54:48.983 * DB loaded from disk: 0.000 seconds
redis_1  | 1:M 16 Aug 17:54:48.984 * Ready to accept connections
api_1    | Starting 'run'...
api_1    | Starting 'db-migrate'...
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist
api_1    | error: database "dev" does not exist
api_1    |     at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:546:11)
api_1    |     at Connection.parseMessage (/usr/src/app/node_modules/pg/lib/connection.js:371:19)
api_1    |     at Socket. (/usr/src/app/node_modules/pg/lib/connection.js:114:22)
api_1    |     at emitOne (events.js:115:13)
api_1    |     at Socket.emit (events.js:210:7)
api_1    |     at addChunk (_stream_readable.js:252:12)
api_1    |     at readableAddChunk (_stream_readable.js:239:11)
api_1    |     at Socket.Readable.push (_stream_readable.js:197:10)
api_1    |     at TCP.onread (net.js:589:20)
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1012ms
api_1    | Node.js API server is listening on http://api:8080/
db_1     | FATAL:  database "dev" does not exist
db_1     | FATAL:  database "dev" does not exist

I see "Node.js API server is listening on ..." it means that the app is running, you should be able to access it via http://localhost:8080/.. Regarding "database dev does not exist", one way is to remove the volume created during the initial run of the docker-compose up and try again, you can use docker volume ls, docker volume rm .. commands to manipulate volumes.. regarding the env variables, you can check what variables are set inside a container by running docker-compose run --rm --no-deps api printenv

@MikePugs this script is executed during the initial run of docker-compose up when no volumes exist yet => https://github.com/kriasoft/nodejs-api-starter/blob/master/config/postgres-initdb.sh After volumes are created they are staying permanently on your machine and this script is ignored, but you can remove volumes manually if needed (see comment above).

Here are the environment variables returned by the command you provided:
$ docker-compose run --rm --no-deps api printenv
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=api
TWITTER_SECRET=xxxxx
DATABASE_DEBUG=false
GOOGLE_ID=xxxxx.apps.googleusercontent.com
CORS_ORIGIN=http://localhost:3001,http://localhost:3000
FACEBOOK_SECRET=2339bdf25f236a42fc3a18280bf455e8
GOOGLE_SECRET=xxxxx
REDIS_URL=redis://redis:6379/0
DATABASE_URL=postgres://postgres@db:5432/dev
CHOKIDAR_USEPOLLING=true
TWITTER_KEY=xxxxx
FACEBOOK_ID=1821424564802638
SESSION_SECRET=wZjwhFtzQsd7r87W6AZw45Sm
NPM_CONFIG_LOGLEVEL=info
NODE_VERSION=8.3.0
YARN_VERSION=0.27.5
HOME=/home/node

It seems that I am only able to remove a volume after I remove the associated container. Otherwise, I receive the following error:
$ docker volume rm exampleapi_db
Error response from daemon: unable to remove volume: remove exampleapi_db: volume is in use - [83bd33a561f45347e6fb827914ae930e0f6177b5d8b31f37b8e2de4378c04249]

After I remove all of the containers and all of the volumes I still receive the previous docker-compose up errors
No Containers:
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

No Volumes:
$ docker volume ls
DRIVER              VOLUME NAME

docker-compose up
$ docker-compose up
Creating volume "exampleapi_redis" with default driver
Creating volume "exampleapi_db" with default driver
Creating volume "exampleapi_yarn" with default driver
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_redis_1
Creating exampleapi_redis_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_db_1, exampleapi_redis_1, exampleapi_api_1, exampleapi_nginx_1
db_1     | The files belonging to this database system will be owned by user "postgres".
db_1     | This user must also own the server process.
db_1     |
redis_1  | 1:C 16 Aug 19:21:48.294 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
db_1     | The database cluster will be initialized with locale "en_US.utf8".
redis_1  | 1:C 16 Aug 19:21:48.294 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
db_1     | The default database encoding has accordingly been set to "UTF8".
redis_1  | 1:C 16 Aug 19:21:48.294 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | The default text search configuration will be set to "english".
redis_1  | 1:M 16 Aug 19:21:48.294 * Running mode=standalone, port=6379.
db_1     |
redis_1  | 1:M 16 Aug 19:21:48.294 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     | Data page checksums are disabled.
redis_1  | 1:M 16 Aug 19:21:48.294 # Server initialized
db_1     |
redis_1  | 1:M 16 Aug 19:21:48.295 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1  | 1:M 16 Aug 19:21:48.295 * Ready to accept connections
db_1     | fixing permissions on existing directory /var/lib/postgresql/data ... ok
db_1     | creating subdirectories ... ok
db_1     | selecting default max_connections ... 100
db_1     | selecting default shared_buffers ... 128MB
db_1     | selecting dynamic shared memory implementation ... posix
db_1     | creating configuration files ... ok
db_1     | running bootstrap script ... ok
db_1     | performing post-bootstrap initialization ... No usable system locales were found.
db_1     | Use the option "--debug" to see details.
db_1     | sh: locale: not found
db_1     | ok
db_1     | syncing data to disk ... ok
db_1     |
db_1     | Success. You can now start the database server using:
db_1     |
db_1     |     pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1     |
db_1     |
db_1     | WARNING: enabling "trust" authentication for local connections
db_1     | You can change this by editing pg_hba.conf or using the option -A, or
db_1     | --auth-local and --auth-host, the next time you run initdb.
db_1     | ****************************************************
db_1     | WARNING: No password has been set for the database.
db_1     |          This will allow anyone with access to the
db_1     |          Postgres port to access your database. In
db_1     |          Docker's default configuration, this is
db_1     |          effectively any other container on the same
db_1     |          system.
db_1     |
db_1     |          Use "-e POSTGRES_PASSWORD=password" to set
db_1     |          it in "docker run".
db_1     | ****************************************************
db_1     | waiting for server to start....LOG:  could not bind IPv6 socket: Address not available
db_1     | HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
db_1     | LOG:  database system was shut down at 2017-08-16 19:21:49 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
db_1     |  done
db_1     | server started
db_1     | ALTER ROLE
db_1     |
db_1     |
db_1     | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/initdb.sh
db_1     | /docker-entrypoint-initdb.d/initdb.sh: line 2: $'\r': command not found
exampleapi_db_1 exited with code 127
api_1    | Starting 'run'...
api_1    | Starting 'db-migrate'...
api_1    | Error: getaddrinfo EAI_AGAIN db:5432
api_1    |     at Object._errnoException (util.js:1022:11)
api_1    |     at errnoException (dns.js:58:15)
api_1    |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:95:26)
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1689ms
api_1    | Node.js API server is listening on http://api:8080/

I see, it complains about the \r symbol in the config/postgres-initdb.sh file. I just added .sh extension to .gitattributes in a8f4663614c7d8d954a189ee93d96fb7b27aacf7. Try merging this update into your project, removing db volume and running docker-compose up again.
git remote add nodejs-api-starter https://github.com/kriasoft/nodejs-api-starter.git
git checkout master
git fetch nodejs-api-starter
git merge nodejs-api-starter/master

I'm not sure I did the git update correctly, or if I continued to experience issues because it wasn't just the last \r that caused the error.
I solved that particular \r error by running the following:
sed -i 's/\r//' config/postgres-initdb.sh

which I believe replaces all of the \r characters in the file*.
After I ran that command, removed all containers and volumes the '\r' error went away. Note the line that says LOG:  received fast shutdown request` though...
$ docker-compose up
Creating volume "exampleapi_redis" with default driver
Creating volume "exampleapi_db" with default driver
Creating volume "exampleapi_yarn" with default driver
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_redis_1
Creating exampleapi_db_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_redis_1, exampleapi_db_1, exampleapi_api_1, exampleapi_nginx_1
redis_1  | 1:C 16 Aug 20:28:51.372 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1  | 1:C 16 Aug 20:28:51.372 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1  | 1:C 16 Aug 20:28:51.372 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | The files belonging to this database system will be owned by user "postgres".
redis_1  | 1:M 16 Aug 20:28:51.373 * Running mode=standalone, port=6379.
db_1     | This user must also own the server process.
redis_1  | 1:M 16 Aug 20:28:51.373 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     |
redis_1  | 1:M 16 Aug 20:28:51.373 # Server initialized
db_1     | The database cluster will be initialized with locale "en_US.utf8".
redis_1  | 1:M 16 Aug 20:28:51.373 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
db_1     | The default database encoding has accordingly been set to "UTF8".
redis_1  | 1:M 16 Aug 20:28:51.373 * Ready to accept connections
db_1     | The default text search configuration will be set to "english".
db_1     |
db_1     | Data page checksums are disabled.
db_1     |
db_1     | fixing permissions on existing directory /var/lib/postgresql/data ... ok
db_1     | creating subdirectories ... ok
db_1     | selecting default max_connections ... 100
db_1     | selecting default shared_buffers ... 128MB
db_1     | selecting dynamic shared memory implementation ... posix
db_1     | creating configuration files ... ok
db_1     | running bootstrap script ... ok
db_1     | performing post-bootstrap initialization ... sh: locale: not found
db_1     | No usable system locales were found.
db_1     | Use the option "--debug" to see details.
db_1     | ok
db_1     | syncing data to disk ...
db_1     | WARNING: enabling "trust" authentication for local connections
db_1     | You can change this by editing pg_hba.conf or using the option -A, or
db_1     | --auth-local and --auth-host, the next time you run initdb.
db_1     | ok
db_1     |
db_1     | Success. You can now start the database server using:
db_1     |
db_1     |     pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1     |
db_1     | ****************************************************
db_1     | WARNING: No password has been set for the database.
db_1     |          This will allow anyone with access to the
db_1     |          Postgres port to access your database. In
db_1     |          Docker's default configuration, this is
db_1     |          effectively any other container on the same
db_1     |          system.
db_1     |
db_1     |          Use "-e POSTGRES_PASSWORD=password" to set
db_1     |          it in "docker run".
db_1     | ****************************************************
db_1     | waiting for server to start....LOG:  could not bind IPv6 socket: Address not available
db_1     | HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
db_1     | LOG:  database system was shut down at 2017-08-16 20:28:52 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
db_1     |  done
db_1     | server started
db_1     | ALTER ROLE
db_1     |
db_1     |
db_1     | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/initdb.sh
api_1    | Starting 'run'...
db_1     | CREATE DATABASE
db_1     | CREATE EXTENSION
db_1     | CREATE EXTENSION
db_1     |
db_1     | LOG:  received fast shutdown request
db_1     | LOG:  aborting any active transactions
db_1     | LOG:  autovacuum launcher shutting down
db_1     | waiting for server to shut down....LOG:  shutting down
db_1     | LOG:  database system is shut down
api_1    | Starting 'db-migrate'...
api_1    | Error: connect ECONNREFUSED <IP_ADDRESS>:5432
api_1    |     at Object._errnoException (util.js:1022:11)
api_1    |     at _exceptionWithHostPort (util.js:1045:20)
api_1    |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1161:14)
api_1    | Starting 'build'...
db_1     |  done
db_1     | server stopped
db_1     |
db_1     | PostgreSQL init process complete; ready for start up.
db_1     |
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/db.js -> build/db.js
api_1    | src/app.js -> build/app.js
api_1    | src/email.js -> build/email.js
db_1     | LOG:  database system was shut down at 2017-08-16 20:28:57 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1172ms
api_1    | Node.js API server is listening on http://api:8080/

The next step of seeding the database understandably throws errors as a result:
winpty docker-compose exec api yarn db-seed

yarn db-seed v0.27.5
$ node tools/db.js seed
Starting 'db-seed'...
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
db_1     | ERROR:  relation "users" does not exist at character 13
db_1     | STATEMENT:  insert into "users" ("display_name", "emails", "image_url") values ($1, $2, $3) returning "id"
error: relation "users" does not exist
    at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:546:11)
    at Connection.parseMessage (/usr/src/app/node_modules/pg/lib/connection.js:371:19)
    at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:114:22)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at addChunk (_stream_readable.js:252:12)
    at readableAddChunk (_stream_readable.js:239:11)
    at Socket.Readable.push (_stream_readable.js:197:10)
    at TCP.onread (net.js:589:20)
Done in 4.07s.

Related*:
https://stackoverflow.com/questions/11616835/r-command-not-found-bashrc-bash-profile

I went to my home computer, deleted the repository, containers, volumes and started over.
It seems to have worked now. Further research suggests that the "fast shutdown" described above is normal behavior.
Here is the output which resulted in what seems to be a successful install on my windows 10 machine

$ docker-compose up
Creating volume "exampleapi_redis" with default driver
Creating volume "exampleapi_db" with default driver
Creating volume "exampleapi_yarn" with default driver
Creating exampleapi_redis_1 ...
Creating exampleapi_db_1 ...
Creating exampleapi_redis_1
Creating exampleapi_db_1 ... done
Creating exampleapi_api_1 ...
Creating exampleapi_api_1 ... done
Creating exampleapi_nginx_1 ...
Creating exampleapi_nginx_1 ... done
Attaching to exampleapi_redis_1, exampleapi_db_1, exampleapi_api_1, exampleapi_nginx_1
redis_1  | 1:C 17 Aug 00:36:53.169 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1  | 1:C 17 Aug 00:36:53.169 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1  | 1:C 17 Aug 00:36:53.169 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     | The files belonging to this database system will be owned by user "postgres".
redis_1  | 1:M 17 Aug 00:36:53.170 * Running mode=standalone, port=6379.
db_1     | This user must also own the server process.
redis_1  | 1:M 17 Aug 00:36:53.170 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
db_1     |
redis_1  | 1:M 17 Aug 00:36:53.170 # Server initialized
redis_1  | 1:M 17 Aug 00:36:53.170 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
db_1     | The database cluster will be initialized with locale "en_US.utf8".
redis_1  | 1:M 17 Aug 00:36:53.170 * Ready to accept connections
db_1     | The default database encoding has accordingly been set to "UTF8".
db_1     | The default text search configuration will be set to "english".
db_1     |
db_1     | Data page checksums are disabled.
db_1     |
db_1     | fixing permissions on existing directory /var/lib/postgresql/data ... ok
db_1     | creating subdirectories ... ok
db_1     | selecting default max_connections ... 100
db_1     | selecting default shared_buffers ... 128MB
db_1     | selecting dynamic shared memory implementation ... posix
db_1     | creating configuration files ... ok
db_1     | running bootstrap script ... ok
db_1     | performing post-bootstrap initialization ... sh: locale: not found
db_1     | No usable system locales were found.
db_1     | Use the option "--debug" to see details.
db_1     | ok
db_1     | syncing data to disk ... ok
db_1     |
db_1     | Success. You can now start the database server using:
db_1     |
db_1     |     pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1     |
db_1     |
db_1     | WARNING: enabling "trust" authentication for local connections
db_1     | You can change this by editing pg_hba.conf or using the option -A, or
db_1     | --auth-local and --auth-host, the next time you run initdb.
db_1     | ****************************************************
db_1     | WARNING: No password has been set for the database.
db_1     |          This will allow anyone with access to the
db_1     |          Postgres port to access your database. In
db_1     |          Docker's default configuration, this is
db_1     |          effectively any other container on the same
db_1     |          system.
db_1     |
db_1     |          Use "-e POSTGRES_PASSWORD=password" to set
db_1     |          it in "docker run".
db_1     | ****************************************************
db_1     | waiting for server to start....LOG:  could not bind IPv6 socket: Address not available
db_1     | HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
db_1     | LOG:  database system was shut down at 2017-08-17 00:36:55 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
db_1     |  done
db_1     | server started
db_1     | ALTER ROLE
db_1     |
db_1     |
db_1     | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/initdb.sh
db_1     | CREATE DATABASE
db_1     | CREATE EXTENSION
db_1     | CREATE EXTENSION
db_1     |
db_1     | LOG:  received fast shutdown request
db_1     | LOG:  aborting any active transactions
db_1     | LOG:  autovacuum launcher shutting down
db_1     | LOG:  shutting down
db_1     | waiting for server to shut down....LOG:  database system is shut down
api_1    | Starting 'run'...
db_1     |  done
db_1     | server stopped
db_1     |
db_1     | PostgreSQL init process complete; ready for start up.
db_1     |
db_1     | LOG:  database system was shut down at 2017-08-17 00:36:56 UTC
db_1     | LOG:  MultiXact member wraparound protections are now enabled
db_1     | LOG:  database system is ready to accept connections
db_1     | LOG:  autovacuum launcher started
api_1    | Starting 'db-migrate'...
api_1    | Finished 'db-migrate' after 280ms
api_1    | Starting 'build'...
api_1    | src/DataLoaders.js -> build/DataLoaders.js
api_1    | src/app.js -> build/app.js
api_1    | src/db.js -> build/db.js
api_1    | src/email.js -> build/email.js
api_1    | src/passport.js -> build/passport.js
api_1    | src/redis.js -> build/redis.js
api_1    | src/server.js -> build/server.js
api_1    | src/routes/account.js -> build/routes/account.js
api_1    | src/schema/Comment.js -> build/schema/Comment.js
api_1    | src/schema/CommentType.js -> build/schema/CommentType.js
api_1    | src/schema/EmailType.js -> build/schema/EmailType.js
api_1    | src/schema/Node.js -> build/schema/Node.js
api_1    | src/schema/README.md -> build/schema/README.md
api_1    | src/schema/Story.js -> build/schema/Story.js
api_1    | src/schema/StoryType.js -> build/schema/StoryType.js
api_1    | src/schema/User.js -> build/schema/User.js
api_1    | src/schema/UserType.js -> build/schema/UserType.js
api_1    | src/schema/ValidationError.js -> build/schema/ValidationError.js
api_1    | src/schema/index.js -> build/schema/index.js
api_1    | src/emails/welcome/html.hbs -> build/emails/welcome/html.js
api_1    | src/emails/welcome/subject.hbs -> build/emails/welcome/subject.js
api_1    | Finished 'build' after 1417ms
api_1    | Node.js API server is listening on http://api:8080/
Thanks for the help.

Great to hear your issue is now resolved! @MikePugs  👍
I thought I would find the same issue in this thread but it seems not so, my issue is slightly different please let me know if I should open a new issue.
I followed the steps in this article:
https://medium.com/@daveyedwards/how-to-setup-kriasofts-nodejs-api-starter-on-windows-10-a092d6e34882
I also ran docker-compose build because it had permission issues as well installing what I think are the dependencies...
But when I ran docker-compose run this happens:
api_1    | yarn install v1.1.0                                                                                api_1    | [1/4] Resolving packages...                                                                                api_1    | [2/4] Fetching packages...                                                                                api_1    | info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.                                                                                api_1    | info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.                                                                api_1    | [3/4] Linking dependencies...                                                                                api_1    | error Could not write file "/usr/src/app/yarn-error.log": "EACCES: permission denied, open '/usr/src/app/yarn-error.log'"                                                      api_1    | error An unexpected error occurred: "EACCES: permission denied, mkdir '/usr/src/app/node_modules'".                                                                            api_1    | info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.                                                                                api_1    | module.js:529                                                                                api_1    |     throw err;                                                                                api_1    |     ^                                                                                api_1    |                                                                                api_1    | Error: Cannot find module 'del'                                                                                api_1    |     at Function.Module._resolveFilename (module.js:527:15)                                                                                api_1    |     at Function.Module._load (module.js:476:23)                                                                                api_1    |     at Module.require (module.js:568:17)                                                                                api_1    |     at require (internal/module.js:11:18)                                                                                api_1    |     at Object.<anonymous> (/usr/src/app/tools/build.js:13:13)                                                                                api_1    |     at Module._compile (module.js:624:30)                                                                                api_1    |     at Object.Module._extensions..js (module.js:635:10)                                                                                api_1    |     at Module.load (module.js:545:32)                                                                                api_1    |     at tryModuleLoad (module.js:508:12)                                                                                api_1    |     at Function.Module._load (module.js:500:3)                                                                                nas_api_1 exited with code 1

I'd really appreciate any help :( This is a fantastic project!

@psyanite the error says that there are missing NPM modules (e.g. node_modules/del). You can try removing node_modules folder and install NPM dependencies from scratch:
$ docker-compose run --rm --no-deps api yarn    # Installs deps inside the "api" container

Thank's @koistya! I'll give it a try and open another issue or something if needed, but I think it's a windows bug that there are some permission issues. Cheers :taiwan: :cake:

I just removed Docker dependency, it should work fine on Windows, all you need is just Node.js 10+ runtime, Yarn and a local or remote instance of PostgreSQL server.


layout caching key doesn't take into account the direction

we can now also make this non-static and use a decorator (as we can now inject the constraint solver into the Grid renderer)


Increase speed of z score calcuations

This code significantly increases the speed of z score calculation.

The way we remove potential outliers has changed - now we remove the top ~20% of values before calculating mean and sd (rather than relying on a sd based approach for outlier detection.  This will also have the effect of reducing the calculated mean a bit (which will slightly inflate the z score for all values) but should reduce the sd enough to help us catch real peaks).
I now automatically add gaussian padding to all missing values from the original array.  This means we can now more easily take advantage of the numpy under the hood optimizations.

Still missing - need to add some tests for the changes that I have made.

At the risk of further increasing my technical debt I am going to merge this so that the speed optimized code can be used in the Google Cloud Functions.


dsl: Implementation of new interpolation methods

Hi Guys @FabioLuporini @mloubout @navjotk @georgebisbas ,
I've been working with @nogueirapeterson to include new interpolation techniques on Devito. We implement the cubic and sinc interpolation methods. Thus, we create two new classes: CubicInterpolator and SincInterpolator, which contains, respectively, the cubic and sinc interpolation methods.
The cubic interpolator was implemented using the cubic convolution technique (10.1109/TASSP.1981.1163711) and the sinc interpolator was implemented using Kaiser windowed sinc functions (https://doi.org/10.1190/1.1451454).
We hope you appreciate this contribution and help us to improve this implementation with your great review!

The .h file shouldn't really be necessary. Bessel function are defined in math.h so should be able to make a symbolic expression directly calling it rather than the lookup table

Also, I want to understand if this is significantly different from using PrecomputedInterpolator (i.e. this class could extend and use the functionality there)

Also, I want to understand if this is significantly different from using PrecomputedInterpolator (i.e. this class could extend and use the functionality there)

At the same way that linear interpolation, both cubic and sinc interpolation also can be done by using PrecomputedInterpolator, if the right coefficients are used. So I can say that the main difference is that this new classes removes the responsibility of obtaining the interpolation coefficients from the user.

@guaacoelho But LinearInterpolator does not do any pre computation. If this class is doing pre computation of coefficients, it could store them in the properties provided by PrecomputedInterpolator and use the rest of the infrastructure there. i.e. This class precomputes the coefficients and hands them off to PrecomputedInterpolator, not the user.

FYI sparse interpolation is beeing revamp in #2128  which should help updae this PR.

sinc interpolation added in #2342 , closing.
Feel free to open a new PR for cubic with the new API.


Likebtn branch

This pull request is implementing a throbbing heart like Button.
The issue is currently closed but as I mentioned before, I liked to work on it and did it similar to the star-button.
As described in the issue an animation was added to scale the size and a text-shadow was added to the heart-icon.
To add dispersing dots afaik a surrounding container would be necessary to contain outcoming dots and position them behind the heart-icon.
Issue: #225

Dear @shahednasser your I made the changes you requested =)
and thank you for the opportunity to make a contribution to this project!

Dear @shahednasser,
thank you for your note. I added the animated class to the like-button now and ran npm compile again as you requested.

Amazing work thanks!
@all-contributors please add @richieracoon for code and idea


chore: jsonfmt portal

Ran jsonfmt -w "specification/portal/**/*.json"

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Can one of the admins verify this patch?


Respect spring.cloud.config.name value in ServiceMatcher

To get notified about changes in properties/yml files that are not named after the service name but
still get pulled from the config server, the value of spring.cloud.config.name is now honored in
addition to the service id when matching destination service ids of incoming RemoteRefreshEvents.
Fixes GH-132

Can you please revert the formatting changes

I imported the formatter settings as described in the contribution guide and executed „format“ on the file in Eclipse. I was surprised by the formatting changes, too. So obviously something went wrong on my side? Will fix it…

Not necessarily, some older files were created before proper standards were used :-)

Reverted the unwanted formatting changes.


Align efforts for WCAG 2.2 compliance

Background

Align testing, compliance, and roadmap efforts with the upcoming WCAG 2.2 release (scheduled for late 2021). We might need to refactor some work done in the first 6 months.
Expected timeline

Steps to complete this goal

Consider the impact of WCAG 2.2. and the work needed to align the following items:

[ ] #10
[ ] #11
[ ] #12

@isabela-pf  to check the status of WCAG 2.2
new in WCAG 2.2

[ ] review how big the changes were from draft to final 2.1 WCAG
[ ] start aligning with WCAG 2.2


Djinni's optional generates an NSNumber on iOS

When using a Djinni's optional<enum> in a record type, the generated Objective-C property becomes an NSNumber
measurements_status = enum {
	no_results;
	results_found;
}

measurements = record {
	measurementsStatus: optional<measurements_status>;
}

generates on ObjC
@property (nonatomic, readonly, nullable) NSNumber * measurementsStatus;

After some digging, it might be related to line 118 in ObjcMarshal.scala but I might have been mistaken
  def toObjcType(ty: TypeRef): (String, Boolean) = toObjcType(ty.resolved, false)
  def toObjcType(ty: TypeRef, needRef: Boolean): (String, Boolean) = toObjcType(ty.resolved, needRef)
  def toObjcType(tm: MExpr): (String, Boolean) = toObjcType(tm, false)
  def toObjcType(tm: MExpr, needRef: Boolean): (String, Boolean) = {
    def args(tm: MExpr) = if (tm.args.isEmpty) "" else tm.args.map(toBoxedParamType).mkString("<", ", ", ">")
    def f(tm: MExpr, needRef: Boolean): (String, Boolean) = {
      tm.base match {
        case MOptional =>
          // We use "nil" for the empty optional.
          assert(tm.args.size == 1)
          val arg = tm.args.head
          arg.base match {
            case MOptional => throw new AssertionError("nested optional?")
            case m => f(arg, true)
          }
        case o =>
          val base = o match {
            case p: MPrimitive => if (needRef) (p.objcBoxed, true) else (p.objcName, false)
            case MString => ("NSString", true)
            case MDate => ("NSDate", true)
            case MBinary => ("NSData", true)
            case MOptional => throw new AssertionError("optional should have been special cased")
            case MList => ("NSArray" + args(tm), true)
            case MSet => ("NSSet" + args(tm), true)
            case MMap => ("NSDictionary" + args(tm), true)
            case d: MDef => d.defType match {
              case DEnum => if (needRef) ("NSNumber", true) else (idObjc.ty(d.name), false)
              case DRecord => (idObjc.ty(d.name), true)
              case DInterface =>
                val ext = d.body.asInstanceOf[Interface].ext
                if (!ext.objc)
                  (idObjc.ty(d.name), true)
                else
                  (s"id<${idObjc.ty(d.name)}>", false)
            }
            case e: MExtern => e.body match {
              case i: Interface => if(i.ext.objc) (s"id<${e.objc.typename}>", false) else (e.objc.typename, true)
              case _ => if(needRef) (e.objc.boxed, true) else (e.objc.typename, e.objc.pointer)
            }
            case p: MParam => throw new AssertionError("Parameter should not happen at Obj-C top level")
          }
          base
      }
    }
    f(tm, needRef)
  }

Any help would be much appreciated

That behavior is by-design.  What were you expecting instead?  I don't know of another obvious way to represent an optional enum in Objective-C in a safe way.  Boxed types allow nullability, and and NSNumber is expected way to box enums in Objective-C.

Apologies, I have been using Swift full-time lately and I just forgot that an NSEnum cannot be nullable on Obj-C contrarily to a Swift enum. It is a pain, but nothing Djinni can do about indeed.
Thanks again

Yeah, direct bridging to Swift would be a nice feature add now that ObjC is on its way out, but I don't know of anyone currently putting the the effort into that for Djinni.


DEV_ROOT_FRAGMENT patchFlag is set despite compilerOptions.comments = true

Vue version
3.2.39
Link to minimal reproduction
https://codepen.io/21stCenturyJonas/pen/oNdodBR
Steps to reproduce
Notice how the dev and prod versions behave differently and how the element root warning is not logged to the console, despite <a-component> having multiple root nodes in dev and in prod.
What is expected?
The DEV_ROOT_FRAGMENT flag should not be set since the comments won't be stripped and the component will continue to render a fragment in production. Thus, the transition should break in development like it does in production and the respective element root warning for <Transition> children should be logged:
    if (__DEV__ && !isElementRoot(root)) {
      warn(
        `Component inside <Transition> renders non-element root node ` +
          `that cannot be animated.`
      )
    }

What is actually happening?
The compiler assumes that the comment will be stripped in production and sets the DEV_ROOT_FRAGMENT flag, hiding any warnings and causing different runtime behavior.
System Info
No response
Any additional comments?
No response

I suspect this may have the same underlying cause as #6080.
Here's a Playground demonstrating the problem. In DEV mode it fades in, but in PROD mode the transition is skipped.


Make sure ligature carets exist for all ligatures

Make sure we have ligature carets for all ligatures, such as "fi".
We basically need to make sure all the ligatures in the font (including contour tones in #13) have ligature carets in the GDEF table (LigCaretList table at http://www.microsoft.com/typography/otspec/gdef.htm).
Internal bug b/15653110

v2.134/Roboto-Regular.ttf still has this issue; since its GDEF data, I think we can hotfix this in the hinted fonts :)

More internal issues
b/32539815
b/29167895
b/32832716


Disable intercepts in host only mode, supports intercepts only mode

This PR contains the following changes

Disable intercepts while running the tunnel in host only mode.
New command run_intercepts is added that supports intercepts only mode
run certain windows script, only if the user is running the tunnel using admin privileges

@mary-dcouto We need to eliminate two remaining dependencies when run-host mode is invoked:

ZET still requires the device /dev/net/tun is present
ZET still requires elevated privileges on that device

These need to be eliminated because ZET will never use them at all when using run-host mode, and they prevent deploying ZET in a container without special devices and without elevated privileges. This is one of the main goals of the feature, to run in a restricted container with bridge networking where neither of those two requirements can be satisfied.


Abhigyan is added

fixes issue no.3

Hey @CYBER-BRIX
At line 6, write 'github' instead of 'git hub' and encapsulate both key and value in quotes. Make the requested changes and your PR will soon be merged by the maintainers.

Done

When will mine profile can be seen on pledge?
On Mon, May 31, 2021, 9:41 AM Bishal Roy @.***> wrote:

@.**** approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforcauseorg/pledge/pull/500#pullrequestreview-671935284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHPMZN7A2XF3MYNJEJTJXLTQMEA3ANCNFSM45ZEORNQ
.

Hey @CYBER-BRIX, it depends on the project maintainer. As soon as the PR gets merged you will see your profile on the pledge website.

It's been few days since my pull request got accepted but still it
hasn't been updated on the website ,can you tell me how much time normally
it takes?
On Mon, May 31, 2021, 11:14 AM Bishal Roy @.***> wrote:

Hey @CYBER-BRIX https://github.com/CYBER-BRIX, it depends on the
project maintainer. As soon as the PR gets merged you will see your profile
on the pledge website.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforcauseorg/pledge/pull/500#issuecomment-851195602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHPMZLCPOYSSNVPSIIZ2ILTQMO3NANCNFSM45ZEORNQ
.


Convert JSON to ARFF?

hello ... I can not convert a json file to ARFF using your example. The result is that I have this: [ '\n', '@DATA', '\n' ]
I can use the parse, but not the format.
thanks for help

This issue is not in the correct repository, it should have been there https://github.com/julien-f/js-arff
It is my fault because the link in the README was incorrect, it has been fixed now.

You mean the example in the README?
I can parse it successfully and then format it again without any problems.


Logic to detect and drop "empty" text sections

Wiki pages tend to generate a lot of empty text sections due to empty divs, br's etc...try to reduce this noice without impacting the intended whitespace generation

Implemented


Error in md_cols while creating sce

Dear sir,
I am always getting that error message and can't get beyond that stage.
I ensured installing the recent version of R and CATALYST as you previously advised. Also, I am following the recent version published on 17th of Dec 2019.  but the issue unfortunately is not resolved and I can't get beyond that stage
sce <- prepData(fs, panel, md, features = panel$fcs_colname)
Error in prepData(fs, panel, md, features = panel$fcs_colname) :
all(ids %in% md[[md_cols$file]]) is not TRUE
I also did ensure that the md$file_names are the same as in the flowset.
Please advise
Thanks
Samar

Can you give the output of sessionInfo() after loading the CATALYST package? As I write this, 1.10.1 is the latest version.
Also the outputs of md and flowCore::keyword(fs, "FILENAME") could be informative.
Best, Mark


tableschema file not found raises an exception instead of an error message

Related to #285
tableschema infer does_not_exist
Raises an exception instead of showing an error message. I think that it would be nicer for users to have an error message
The same happens with tableschema validate invalid_file. A more succint error message and perhaps a suggestion on how to fix it would be appreciated by users not used to read Python exceptions.
Tableschema version: 1.18

Please preserve this line to notify @roll (lead of this repository)

MERGED into https://github.com/frictionlessdata/tableschema-py/issues/285


[database] allow database to derive startdate/enddate/curdate

It would be preferable to, rather than infer, make the start date, end date and current date of the time slider to be given from the database. They should still be overrideable from the URL

Reopening: this should include starting lat/lon/z as well, those shouldn't be baked into the ohmec.js script


Bring Back Demo Pages from Old HASP Repo

Feature Request
I'm loving the new HASPone setup. However, I do miss the preconfigured alarm panel with colored buttons. I hadn't gotten around to the using the thermostat example yet, but it looked amazing.
Creating our own pages using the button blueprints appears to be much easier than what we had to do before, but colorizing and making them as nice as your demo example does not seem easily possible just yet.
This is just a suggestion, because I love what you are doing with this and I'm glad I bought mine HASP pre-made from you! :D

I think we should have most of the original demo automations covered off with blueprints, including a few variations on HVAC and a newly-update alarm panel blueprint!


After deployment: Excessive user number and many users without properties

Please fill in the following fields:
Unity editor version: 2018.4.9
Firebase Unity SDK version: 6.6
Firebase plugins in use (Auth, Database, etc.): Analytics
Additional SDKs you are using (Facebook, AdMob, etc.):
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows, Mac
Platform you are targeting (iOS, Android, and/or desktop): iOS, Android
Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Configure the Firebase analytics for Unity. Below is my code:
FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith(task => {
	var dependencyStatus = task.Result;
	if (dependencyStatus == DependencyStatus.Available) {
		Firebase = FirebaseApp.DefaultInstance;
		FirebaseAnalytics.SetAnalyticsCollectionEnabled(true);
		FirebaseAnalytics.SetSessionTimeoutDuration(new TimeSpan(0, 30, 0));
		SetUserProperty("Version", Analytics.bundleVersion);
		SetUserProperty("Language", Localized.Language);
		SetUserProperty("ScreenSize", Settings.GetScreenSize().ToString());
		Debug.Log("Firebase started! " + Firebase.Options.AppId);
	} else {
		Debug.LogError(System.String.Format(
			"Could not resolve all Firebase dependencies: {0}", dependencyStatus));
	}
});

However, there are excessive user count reported, many of which without properties like Version, Language and ScreenSize (which is a must for everyone). In realtime view this also happens, e.g the 58 online users have only 42 with properties. Cannot reproduce in my own devices / simulators.
Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
No idea

Hi @CIVITAS-John, can you try add more log information to identify when write to user's property, is it because the dependencyStatus is not Available, or the information that trying to write to user property is empty, or it's written but not recorded in Analytics?

The question is... There is an excessive amount of users. The number of users with properties is almost the same as other analytics (we are still using Google Analytics for reference), but the overall amount is much higher. Also, those without user properties would only send one event (first open) and nothing more.

It is also very weird that user engagement can be in hours...

Again, how can active users beat sessions?

@CIVITAS-John this repo is for issues with the Unity quickstart. Not the correct place for Google Analytics troubleshooting. Please post this on firebase-talk, Stack Overflow, or https://firebase.community/. Feel free to ping me with your post and I'll help you get an answer<EMAIL_ADDRESS>

Hi @CIVITAS-John, did you follow the suggestion and post the issue to any of the other channels? If so could you share the link/id so I can follow up with? Thanks!


epic: Connector: Spark Overhaul

** Children: maintained on a best effort basis:** [#1589, #1659, #1664, #1665, #1666, #1672, #1673, #1674, #1675, #1676, #1689, #1712, #1718, #1725, #1761, #1762, #1763, #1764, #1782,  #1899, #1900, #1907, #1926, #1934, #1980]

[ ] Implement direct codecs that eliminate intermediate transforms
[ ] Do not compile to Spark ops that result in a chokepoint
[ ] Support data frames for regular data
[ ] TBD

File Formats

[ ] Support CSV files
[ ] Support Hive tables
[ ] Support anything with a SerDe
[ ] Support ORC
[ ] Support Avro
[ ] Support XML files
[ ] Support EJSON files

Miscellaneous
Whatever else doesn't fit into the above categories.

@zeeiyerWork Same here, @rabbitonweb can help flesh this out a bit based on known limitations & possible improvements.

will do


capital month names; removed redundant headers

Is the removal of the link to the YouTube channel intentional?

No, it isn't... I think it is because I moved it to a separate section, but I can move it back up if that is better

sorry, I didn't see it was below.

However, I can't run the make script without the following error message:
WARNING: Feeds generated without SITEURL set properly may not be valid ERROR: Skipping pages/2017/descriptions/index.md: could not find information about 'title'

The warning
WARNING: Feeds generated without SITEURL set properly may not be valid

only occurs when building the website locally (i.e. "make html"). It is not present when running "make rsync".
The error
ERROR: Skipping pages/2017/descriptions/index.md: could not find information about 'title'

occurs because of a useless file. I guess we can remove it.


Instagram profile picture does not work

The Instagram endpoint always returns unavatar's logo instead of actually getting the user's profile pic. Is there a way I can get it working?
See example: https://unavatar.io/instagram/annastalksme

Oops, I accidentally closed it - is there a way I can add labels to this issue?

@Kikobeats is this something youre aware of?

I don't think there is much to do if Instagram decides to put the content behind a wall for IP that comes from data centers, we should to disable instagram for a while (we did the same for TikTok in the past)

Ok, thank you. Lmk when/if it gets up and working again!


Enable Link-Time Optimization (LTO) and codegen-units = 1

Hi!
I noticed that in the Cargo.toml file Link-Time Optimization (LTO) for the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance a little bit. If you want to read more about LTO and its possible modes, I recommend starting from this Rustc documentation.
I think you can enable LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional dist or release-lto profile where in addition to regular release optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most optimized version of the application. However, if we enable it on the Cargo profile level for the Release profile, users, who install the application with cargo install will get the LTO-optimized version of the game "automatically". E.g., check cargo-outdated Release profile. You also could be interested in other optimization options like codegen-units = 1, etc.
Basically, it can be enabled with the following lines:
[profile.release]
lto = true

I have made quick tests (Fedora 41, Rust 1.82, the latest version of the project) - here are the results (ls -la):

Release: 13784408 byte
Release + codegen-units = 1: 11506840 byte
Release + LTO: 11538008 byte
Release + codegen-units = 1 + LTO: 10910104 byte

Thank you.

Hi, thanks, this is awesome - I had totally forgotten this!
By enabling the LTO and codegen-units = 1 the binary size drops as you said, but there is also solid 12-16% speed up by all perf tests (perf-setup and cargo run --release -p tackler-core). :clap: :clap::clap:
The release build times are up to 25%, but c'est la vie - it's one time cost.
And thank you for detailed description on this topic.


Re-enable checks for extensions on tests-plugin-build.sh once we have versions of those extensions compliant with 2.10

Re-enable checks for extensions on tests-plugin-build.sh once we have versions of those extensions compliant with 2.10
https://github.com/rancher/dashboard/blob/master/shell/scripts/test-plugins-build.sh#L226-L228

What's the current state of the extension migration? @aalves08 @mantis-toboggan-md @jordojordo
@aalves08 I think this has to be enabled for 2.10.0, no?

@cnotv This depends on the migration of Kubewarden, CAPI 🐢  and Elemental and having working versions of them compliant with 2.10/Vue3 and for that the deadline is 2.10.1, so it won't be re-enabled in 2.10.0 for sure since it won't fit the timeframe we have.
I have noticed that I had wrongfully added the milestone 2.11 to this, so I removed it

This also has dependency with https://github.com/rancher/dashboard/issues/12147

Yes, Typescript become more restrictive, as well as the VueCLI or Webpack.

Will wait a bit more for CAPI to be migrated as well a re-enable the 3 extensions there at once (KW, Elemental and CAPI)


Clearable not working in 0.1.6

Clearable not working properly in tag 0.1.16 but work fine in commit 61f1f4abfb315e853c200209577d9dd893d28563

:+1: Would be nice to have a 0.1.7 release to fix the clearable feature.

Hello, should be fixed


Recursive dictionary lookups cause a crash

From #296

This can be closed. See conversation in https://github.com/NPBruce/valkyrie/pull/296


Release v1.31.0

Feature Request
Describe the problem you need a feature to resolve.
This is a placeholder issue for releasing Operator SDK v1.31.0 following the release guide: https://sdk.operatorframework.io/docs/contribution-guidelines/releasing/

/assign @rashmigottipati

https://github.com/operator-framework/operator-sdk/pull/6522 - Operator SDK 1.31.0 has been released!
https://github.com/operator-framework/operator-sdk/releases/tag/v1.31.0


[ADLA CLI 2.0] Correcting "file" to "fs" in an example's syntax

[ADLA CLI 2.0] Correcting "file" to "fs" in an example's syntax

#sign-off


APP CRASH WHEN RUN ON ANDROID 13 DEVICE

my app use this package worked with anydevice . But when release app and run on device android 13 app crashed.  please tell me if somebody know solutions. thanks

Not sure if our issue is exactly the same: I use the flutter camera package AND the learning_input_image. When starting the camera on an Android 13 device I got an Exception. In my case this was my problem and my fix:
This package depends on the camera package. However not the most updated version of the Camera package (0.9.4+5). In the camera package ^0.9.4+5 there was an Android 13 issue ( https://github.com/flutter/flutter/issues/109769 )The crash is probably originating from there. The camera package issue has been fixed ( camera 0.10.5+4 ), but this package still uses the older version... My advice, until this package gets updated:
dependencies:
flutter:
sdk: flutter
camera: ^0.9.4+5 #use downgraded package
#Add the temporary fix as suggested by Andrew Coutts in issue 109769
dependency_overrides:
camera:
git:
url: https://github.com/bottlepay/plugins.git
path: packages/camera/camera
ref: e1a4dba770da9bc3cf9f858bac6837083f8b9059


com.vividsolutions.jts.geom.TopologyException on SpatialJoinQueryFlat

Expected behavior
I want to decrease geometry (polygon) points float decision or apply convexHull on geometry and expected to have a success join
Actual behavior
TopologyException with description "side location conflict" regardless of decreasing decision / convexHull transformation
Steps to reproduce the problem

I make a dataframe of WKT and then creating a SpatialRDD from DataFrame.

Do CRSTransformation to translate geometry from EPSG:3576 to EPSG:4326 (I tried to remove it, but error still occures)

Trying to decrease decision of points in geometry and do a join

Building indexes and do spatialPartitioning on both RDD in join

Joining

Code looks like that:

def convexHullGeometry(spatialRDD: SpatialRDD[Geometry]): SpatialRDD[Geometry] = {
    val newSpatialRDD = new SpatialRDD[Geometry] // i'have also tried modify rawSpatialRdd on existing spatialRDD without creating a new one

    val rdd = spatialRDD.rawSpatialRDD.rdd
      .map(geom => {
        val userData = geom.getUserData
        val scale = Math.pow(10, 4) // i want to only 4 digits after comma in double
        val newGeom = GeometryPrecisionReducer.reduce(geom, new PrecisionModel(scale))
        // val newGeom = geom.convexHull // another way of rescuing TopologyException
        println(geom.toText)
        println(newGeom.toText)
        newGeom.setUserData(userData)
        newGeom
      })

    newSpatialRDD.rawSpatialRDD = rdd
    newSpatialRDD
  }

So without this transformation code error looks like:
com.vividsolutions.jts.geom.TopologyException: side location conflict [ (55.30554100092851, 52.03084499997882, NaN) ]
When I try to do decreasing decision transformation I got error like this:
com.vividsolutions.jts.geom.TopologyException: side location conflict [ (55.30554100092851, 52.03084499997882, NaN) ]
Why points still have the same double decision? I expected not to see error or to see something like:
[ (55.3055, 52.0308, NaN) ] if I downgrade decision.
Settings
GeoSpark version = 1.1.3
Apache Spark version = 2.2.0
JRE version = 1.8
API type = Scala

@m4nzh Please use ST_PrecisionReduce in GeoSpark 1.2.0-SNAPSHOT
http://datasystemslab.github.io/GeoSpark/api/sql/GeoSparkSQL-Function/#st_precisionreduce
Snapshot coordinate: http://datasystemslab.github.io/GeoSpark/download/GeoSpark-All-Modules-Maven-Central-Coordinates/#snapshot-versions


refactor(firebase_dynamic_links_platform_interface): fix analyze issue introduced in Flutter 3.0.0

Description
Flutter 3.0.0 caused failing the CI: https://github.com/firebase/flutterfire/runs/6398175458?check_suite_focus=true
Nils-MBP-13-M1-3:firebase_dynamic_links_platform_interface nils$ flutter analyze
Running "flutter pub get" in firebase_dynamic_links_platform_interface...      1,220ms
Analyzing firebase_dynamic_links_platform_interface...

warning • The '!' will have no effect because the receiver can't be null • test/mock.dart:78:33 • unnecessary_non_null_assertion

1 issue found. (ran in 2.5s)

Related Issues
Closes #8646
Part of #8644
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

cc: @Salakar (tagging you because it fixes the broken CI pipeline, see #8644)


Add Bitadx Token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: yWrsPP55pxTXWBnuReEd7B1gTFqLsfbhP3ZvnGCdrE4
Token Name: Bitadx
Token Symbol: BTDX
Logo: (https://github.com/bitadx/token-list/blob/1dc1df7e5fe924728bfa1d5924ddf5e6dd36fe0b/assets/mainnet/yWrsPP55pxTXWBnuReEd7B1gTFqLsfbhP3ZvnGCdrE4/logo.png)
Link to the official homepage of token:https://www.bitadx.com

Refer this https://github.com/solana-labs/token-list/pull/5803 i can help.. stop wasting your time!

this PR adds a toplevel solana.tokenlist.json (very bad)


"directyl" on the exposed page on qgis website

http://www.qgis.org/en/site/getinvolved/governance/trademark/index.html linked from main page (http://www.qgis.org/en/site/) has "directyl" misspelling in ("Please routinely explain in your course that QGIS is free and open source software, and actively encourage anyone to contribute, directyl or indirectly, to the project").
migrated from http://hub.qgis.org/issues/14230

Sorry, I was too fast. It is already fixed :)


Fix form issues on create/edit

Prior to this change, when a user withdrawned the create workbasket
date was emtpy. Similar on find and edit group dropdown was empty as
well
This change fixes those two issues by fixing a bug on regulation form
component and with a small tweak to force custom-select work

Approved but @steveholmes do you want to look at the structure.sql changes?


Add logic of logging skipping for given endpoints

Closes #13

Hey @XoMute , This works. Merging.


Stack Overflow beta documentation

cf http://docs-beta.stackexchange.com/documentation/elm
If you have access to this page, you should commit.

I do not have access.

@evancz http://stackoverflow.com/documentation/elm
You do now. Please reopen.


Renewing vault secrets

Hi,
I am going in circles for a while now and maybe someone can help here..
I am using consul as vault backend and getting a renewable lease.
I see that LeaseAwareVaultPropertySource is being used and has my consul token in it.
The token is being renewed but when max ttl is exhausted it is not being renewed or rotated.
As far as I understand it is because RequestedSecert is of mode new and not rotate.
This is the relevant code from LeasingVaultPropertySourceLocator in getRequestedSecret
My question: How can I make the lease renewed once it is expired?
Thanks,
Danny

Thanks for raising this issue. This issue is a duplicate of #85 but we evolved since then.
Service/database secrets configured (requested) through the bootstrap.(properties|yaml) mechanism are renewed only. They are not rotated. This is because these secrets are provided through PropertySources and typically copied into other components that are not notified upon rotation.
We introduced with Spring Cloud Vault 1.1 a configurer API that allows you to request additional secrets along renewal/rotation mode. You can also hook into Vault's SecretLeaseContainer to listen for rotation events. Provide a VaultConfigurer bean within the bootstrap context (@Configuration class and spring.factories entry à la org.springframework.cloud.bootstrap.BootstrapConfiguration=example.customize.CustomConfiguration) to tailor the requested secrets:
@Configuration
public class CustomConfiguration {

	private final SecretLeaseContainer leaseContainer;

	public CustomConfiguration(SecretLeaseContainer leaseContainer) {
		this.leaseContainer = leaseContainer;
	}

	@PostConstruct
	private void postConstruct() {

		leaseContainer.addLeaseListener(event -> {

			if (event instanceof SecretLeaseCreatedEvent
					&& event.getSource().getPath().equals("consul/creds/my-role")) {
				// update Consul token in Consul component

			}
		});
	}

	// Customization of property sources.
	@Bean
	public VaultConfigurer configurer() {

		return configurer -> configurer
				.add(RequestedSecret.rotating("consul/creds/my-role"));
	}
}

See also our customization example: https://github.com/mp911de/spring-cloud-vault-config-samples/tree/master/spring-cloud-vault/customize

Thanks. So will VaultConfigurer bean update the Vault property source?

VaultConfigurer contains the metadata how to build property sources.

Thanks a lot @mp911de
It works perfectly.

Closing this one as everything works as designed.


feat: disjunctive license acknowledgement

fixes #590

renamed class LicenseExpressionAcknowledgement to LicenseAcknowledgement
added deprecated alias LicenseExpressionAcknowledgement for LicenseAcknowledgement
so there is no breaking change
added property DisjunctiveLicense.acknowledgement
added integration test for new properties and structures

@madpah could i ask you for a review?


Python 3.9 OS-X support

Hi Emil/Ilastik team, I was hoping to test out napari-ilastik locally on a mac and ran into issues with fastfilters - it appears the ilastik-forge/fastfilters package only supports up to python 3.8. On Big-Sur and above napari requires the conda-forge version of python 3.9, see here for details.
(napari-ilastik) ➜  fastfilters git:(master) ✗ conda install -c ilastik-forge fastfilters
Collecting package metadata (current_repodata.json): done
Solving environment: -
Found conflicts! Looking for incompatible packages.                                                                                failed

UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:

Specifications:

  - fastfilters -> python[version='>=3.7,<3.8.0a0']

Your python: python=3.9

I tried to build fastfilters locally but ran into issues with both apple clang and conda-forge clang without immediate success but I'm not an expert at compiling these things.
Is updating the fastfilters conda-forge recipe to support 3.9 on your radar? Is compatibility with big-sur macs for napari-ilastik planned to be supported at some point?
Thanks!

Hi @alisterburt,
Unfortunately, upgrading fastfilters to Python 3.8+ is not as straightforward as it seems, so we cannot promise any dates (this is one of the reasons classic ilastik is still on Python 3.7).
Regarding macOS Big Sur, it seems that napari requires only Python 3.7 and later both via conda and via pip. I am personally using napari and fastfilters installed in the same environment on Big Sur.

Thanks for the details/info and sorry to hear it's not as easy as it could be!
Interesting about Big Sur, it may be that 3.9 is only a requirement on the M1 chip then, I'll have a look around

Looks like fastfilters on ilastik-forge supports 3.9 now:
https://anaconda.org/ilastik-forge/fastfilters/files


change the signature of findService() to return InstanceContainer directly

cxx::expected<InstanceContainer, Error> PoshRuntime::findService(const capro::ServiceDescription& serviceDescription) noexcept
This will overcome to deal with issues like:

What to do if the provided InstanceContainer is full
If we found a service should we look in the InstanceContainer if its already present.
What is with entries which are out of date?

reference: #240

fixed with #240


Remove CircleCI

We decided for using Github Actions instead

@suprMax thanks for setting up CircleCI - please disable it again (I can't do it)

done


Help finish phragmen benchmarks

This PR attempts to get phragmen benchmarks #5845  to a point I am happy to approve :)

Looks good and will merge in now, but I think the original one still has some panics as well.


fix failing tests

I want to merge this change because I fixed or skipped failing tests

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-3704 Fix failing cypress tests