having issues with running the docker-compose up command for starting articulate

Issues

If you're having trouble with Articulate we definitely want to help you. If you can provide a little bit of information it will make our troubleshooting job easier.

Please describe the issue you are having here and answer the question below.

Did you download a release or pull from Master? Which release? release
What operating system are you running? Windows 10 Pro
Are you running locally or in the cloud? locally
Which browser are you using? Chrome

I am new to articulate. I have downloaded the docker for windows. Tried running the docker-compose up command on shell but it takes forever to load articulate. It has consumed close to 10GBof my data. I am a bit confused as to what the problem really is.
If possible provide the use case for the feature and how you would use it.
 Make sure your C drive (or the drive you are trying to run from) has a check mark by it in this window: https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-windows-volumes/

Hey @Chiagoro-ahaotu it needs access to your C drive. Make sure your C drive (or the drive you are trying to run from) has a check mark by it in this window: https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-windows-volumes/

Thank you so much for your reply. However, I have not been able to see where I can give docker access to my C drive.
When I open my docker settings, I only see these options: "General, Proxies, Daemon and Reset", no shared devices in the options.

I was running on the windows mode. Switched to Linux and found it

Good to hear. Let us know if you have any other troubles.

One more thing, which of these do you recommend to download the articulate-master or the latest version V.0.22.0.
I am downloading the V.0.22.0 right now, do I download and unzip the 3 folders there (articulate and the source code) or just the first zipped file.

I would always download the latest release: https://github.com/samtecspg/articulate/releases
You only need the first file articulate-vX.XX.X.zip, we'll update the docs to specify this. You unzip and cd into that folder then docker-compose up
https://samtecspg.github.io/articulate/#/getting-started/basic-installation.md#setup

Thank you. I will hit you up if I encounter any other problem.

It came up with this error after running on PowerShell prompt. Any idea what the problem is
PS C:\WINDOWS\system32> cd C:\articulate-v0.22.0
PS C:\articulate-v0.22.0> docker-compose up
Creating network "articulate-v0220_default" with the default driver
Creating articulate-v0220_api_1           ... done
Creating articulate-v0220_elasticsearch_1 ... done
Creating articulate-v0220_rasa_1          ... done
Creating articulate-v0220_redis_1         ... done
Creating articulate-v0220_duckling_1      ... done
Creating articulate-v0220_ui_1            ... done
Attaching to articulate-v0220_duckling_1, articulate-v0220_api_1, articulate-v0220_ui_1, articulate-v0220_redis_1, articulate-v0220_elasticsearch_1, articulate-v0220_rasa_1
api_1            | 2019/05/28 13:07:45 Waiting for: http://elasticsearch:9200
api_1            | 2019/05/28 13:07:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: no route to host. Sleeping 1s
api_1            | 2019/05/28 13:07:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
redis_1          | 1:C 28 May 13:07:46.970 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1          | 1:C 28 May 13:07:46.982 # Redis version=4.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1          | 1:C 28 May 13:07:46.982 # Configuration loaded
redis_1          | 1:M 28 May 13:07:47.107 * Running mode=standalone, port=6379.
redis_1          | 1:M 28 May 13:07:47.107 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1          | 1:M 28 May 13:07:47.107 # Server initialized
redis_1          | 1:M 28 May 13:07:47.107 # 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 28 May 13:07:47.108 * Ready to accept connections
api_1            | 2019/05/28 13:07:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:54 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:55 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:07:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | yarn run v1.15.2
api_1            | 2019/05/28 13:07:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | $ cross-env NODE_ENV=production env-cmd .env babel-node server
api_1            | 2019/05/28 13:07:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
api_1            | 2019/05/28 13:08:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:21 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T13:08:23,945][WARN ][o.e.c.l.LogConfigurator  ] [unknown] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace %node_name with [%node_name]%marker  in these locations:
elasticsearch_1  |   /usr/share/elasticsearch/config/log4j2.properties
api_1            | 2019/05/28 13:08:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 13:08:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s

None of those look like errors, just the normal startup process.

Elasticsearch can take several minutes to launch, which is why you see the connection being retried multiple times.

Alright then. Will keep you posted

Ended with Error code 109. Looks like a connection problem but my connection is good. Below is a snippet of the cmd display
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Error http://api:7500
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ERROR: Windows named pipe error: The pipe has been ended. (code: 109)

I need the entire log so we can find where the actual error occurred.

I am running it again. WIll do so when it terminates

After restarting the process, I think the error was resolved. However, I am not sure of what to do next. Here's the log.
 Sleeping 1s
api_1            | 2019/05/28 14:49:38 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:39 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
redis_1          | 1:C 28 May 14:49:37.239 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1          | 1:C 28 May 14:49:37.358 # Redis version=4.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1          | 1:C 28 May 14:49:37.358 # Configuration loaded
redis_1          | 1:M 28 May 14:49:37.455 * Running mode=standalone, port=6379.
redis_1          | 1:M 28 May 14:49:37.455 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1          | 1:M 28 May 14:49:37.455 # Server initialized
redis_1          | 1:M 28 May 14:49:37.455 # 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 28 May 14:49:37.459 * Ready to accept connections
api_1            | 2019/05/28 14:49:40 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:41 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:42 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:43 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:44 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:45 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:46 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:47 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | yarn run v1.15.2
api_1            | 2019/05/28 14:49:48 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | $ cross-env NODE_ENV=production env-cmd .env babel-node server
api_1            | 2019/05/28 14:49:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:54 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
api_1            | 2019/05/28 14:49:55 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:49:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:21 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:50:26,442][WARN ][o.e.c.l.LogConfigurator  ] [unknown] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace %node_name with [%node_name]%marker  in these locations:
elasticsearch_1  |   /usr/share/elasticsearch/config/log4j2.properties
api_1            | 2019/05/28 14:50:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:31 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:33 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:36 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:38 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:39 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:40 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:41 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:42 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:43 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:44 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:45 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:46 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:47 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:48 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:54 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:55 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:50:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:50:59,762][INFO ][o.e.e.NodeEnvironment    ] [hoRa3X6] using [1] data paths, mounts [[/usr/share/elasticsearch/data (//<IP_ADDRESS>/C)]], net usable_space [620.4gb], net total_space [930.4gb], types [cifs]
elasticsearch_1  | [2019-05-28T14:50:59,764][INFO ][o.e.e.NodeEnvironment    ] [hoRa3X6] heap size [495.3mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2019-05-28T14:50:59,823][INFO ][o.e.n.Node               ] [hoRa3X6] node name derived from node ID [hoRa3X66QOGDvLTUGo0r6Q]; set [node.name] to override
elasticsearch_1  | [2019-05-28T14:50:59,824][INFO ][o.e.n.Node               ] [hoRa3X6] version[6.5.1], pid[1], build[default/tar/8c58350/2018-11-16T02:22:42.182257Z], OS[Linux/4.9.125-linuxkit/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13]
elasticsearch_1  | [2019-05-28T14:50:59,825][INFO ][o.e.n.Node               ] [hoRa3X6] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.9rtdxzd9, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.locale.providers=COMPAT, -XX:UseAVX=2, -Des.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.flavor=default, -Des.distribution.type=tar]
duckling_1       | no port specified, defaulting to port 8000
duckling_1       | Listening on http://<IP_ADDRESS>:8000
api_1            | 2019/05/28 14:51:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
rasa_1           | 2019-05-28 14:51:01+0000 [-] Log opened.
rasa_1           | 2019-05-28 14:51:01+0000 [-] Site starting on 5000
rasa_1           | 2019-05-28 14:51:01+0000 [-] Starting factory <twisted.web.server.Site object at 0x7f57ad04ac18>
api_1            | 2019/05/28 14:51:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | ws-proxy-plugin
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | http://ffe59a0fb478:3000
ui_1             | method  path       description
ui_1             | ------  ---------  -----------
ui_1             | AUTH    /nes/auth
ui_1             |
ui_1             | Server started ! ✓
ui_1             |
ui_1             | Access URLs:
ui_1             | -----------------------------------
ui_1             | Localhost: http://localhost:3000
ui_1             |       LAN: http://<IP_ADDRESS>:3000
ui_1             | -----------------------------------
ui_1             | Press CTRL-C to stop
ui_1             |
ui_1             | http://ffe59a0fb478:3000
ui_1             | method  path           description
ui_1             | ------  -------------  -----------
ui_1             | *       /api/{paths*}
ui_1             | AUTH    /nes/auth
ui_1             |
api_1            | 2019/05/28 14:51:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:51:12,281][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2019-05-28T14:51:12,282][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [analysis-common]
elasticsearch_1  | [2019-05-28T14:51:12,282][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [ingest-common]
elasticsearch_1  | [2019-05-28T14:51:12,282][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [lang-expression]
elasticsearch_1  | [2019-05-28T14:51:12,283][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [lang-mustache]
elasticsearch_1  | [2019-05-28T14:51:12,283][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [lang-painless]
elasticsearch_1  | [2019-05-28T14:51:12,283][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [mapper-extras]
elasticsearch_1  | [2019-05-28T14:51:12,283][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [parent-join]
elasticsearch_1  | [2019-05-28T14:51:12,284][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [percolator]
elasticsearch_1  | [2019-05-28T14:51:12,284][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [rank-eval]
elasticsearch_1  | [2019-05-28T14:51:12,284][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [reindex]
elasticsearch_1  | [2019-05-28T14:51:12,284][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [repository-url]
elasticsearch_1  | [2019-05-28T14:51:12,285][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [transport-netty4]
elasticsearch_1  | [2019-05-28T14:51:12,286][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [tribe]
elasticsearch_1  | [2019-05-28T14:51:12,286][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-ccr]
elasticsearch_1  | [2019-05-28T14:51:12,287][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-core]
elasticsearch_1  | [2019-05-28T14:51:12,287][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-deprecation]
elasticsearch_1  | [2019-05-28T14:51:12,287][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-graph]
elasticsearch_1  | [2019-05-28T14:51:12,287][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-logstash]
elasticsearch_1  | [2019-05-28T14:51:12,288][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-ml]
elasticsearch_1  | [2019-05-28T14:51:12,288][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-monitoring]
elasticsearch_1  | [2019-05-28T14:51:12,288][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-rollup]
elasticsearch_1  | [2019-05-28T14:51:12,289][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-security]
elasticsearch_1  | [2019-05-28T14:51:12,289][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-sql]
elasticsearch_1  | [2019-05-28T14:51:12,289][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-upgrade]
elasticsearch_1  | [2019-05-28T14:51:12,289][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded module [x-pack-watcher]
elasticsearch_1  | [2019-05-28T14:51:12,290][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded plugin [ingest-geoip]
elasticsearch_1  | [2019-05-28T14:51:12,291][INFO ][o.e.p.PluginsService     ] [hoRa3X6] loaded plugin [ingest-user-agent]
api_1            | 2019/05/28 14:51:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:21 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:51:30,039][INFO ][o.e.d.DiscoveryModule    ] [hoRa3X6] using discovery type [single-node] and host providers [settings]
api_1            | 2019/05/28 14:51:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/05/28 14:51:31 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:51:31,622][INFO ][o.e.n.Node               ] [hoRa3X6] initialized
elasticsearch_1  | [2019-05-28T14:51:31,623][INFO ][o.e.n.Node               ] [hoRa3X6] starting ...
elasticsearch_1  | [2019-05-28T14:51:32,089][INFO ][o.e.t.TransportService   ] [hoRa3X6] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
api_1            | 2019/05/28 14:51:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-05-28T14:51:32,250][INFO ][o.e.h.n.Netty4HttpServerTransport] [hoRa3X6] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
elasticsearch_1  | [2019-05-28T14:51:32,253][INFO ][o.e.n.Node               ] [hoRa3X6] started
elasticsearch_1  | [2019-05-28T14:51:32,564][INFO ][o.e.l.LicenseService     ] [hoRa3X6] license [3ba1f4d3-b71c-4a71-ab7f-5155ffa1c3e7] mode [basic] - valid
elasticsearch_1  | [2019-05-28T14:51:32,570][INFO ][o.e.g.GatewayService     ] [hoRa3X6] recovered [0] indices into cluster_state
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | 2019/05/28 14:51:33 Received 200 from http://elasticsearch:9200
api_1            | yarn run v1.15.2
api_1            | $ nodemon server --exec babel-node
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
api_1            | [nodemon] 1.18.10
api_1            | [nodemon] reading config ./package.json
api_1            | [nodemon] to restart at any time, enter rs
api_1            | [nodemon] or send SIGHUP to 27 to restart
api_1            | [nodemon] ignoring: ./node_modules/**/*
api_1            | [nodemon] watching: .
api_1            | [nodemon] watching extensions: js,mjs,json
api_1            | [nodemon] starting babel-node server
api_1            | [nodemon] spawning
api_1            | [nodemon] child pid: 40
api_1            | [nodemon] watching 344 files
ui_1             | webpack built b20af1f1abda0cec4eff in 41171ms
ui_1             | ℹ ｢wdm｣: Compiled with warnings.
ui_1             | ⚠ ｢wdm｣: Hash: b20af1f1abda0cec4eff
ui_1             | Version: webpack 4.12.0
ui_1             | Time: 41171ms
ui_1             | Built at: 05/28/2019 2:51:44 PM
ui_1             |                                             Asset       Size  Chunks                    Chunk Names
ui_1             |                   6.ad682d1011ae2dee3da1.chunk.js   39.6 KiB       6  [emitted]
ui_1             |             ffcc050b2d92d4b14a4fcb527ee0bcc8.woff   21.1 KiB          [emitted]
ui_1             |            285467176f7fe6bb6a9c6873b3dad2cc.woff2   15.2 KiB          [emitted]
ui_1             |             de8b7431b74642e830af4d4f4b513ec9.woff   19.5 KiB          [emitted]
ui_1             |             9680d5a0c32d2fd084e07bbc4c8b2923.woff     21 KiB          [emitted]
ui_1             |                                     .htaccess.bin   1.75 KiB          [emitted]
ui_1             |            7b770d6c53423deb1a8e49d3c9175184.woff2   16.8 KiB          [emitted]
ui_1             |            6232f43d15b0e7a0bf0fe82e295bdd06.woff2   16.3 KiB          [emitted]
ui_1             |             bafb105baeb22d965c70fe52ba6b49d9.woff   19.4 KiB          [emitted]
ui_1             |             e9dbbe8a693dd275c16d32feb101f1c1.woff   19.5 KiB          [emitted]
ui_1             |            5d4aeb4e5f5ef754e307d7ffaef688bd.woff2     15 KiB          [emitted]
ui_1             |             d704bb3d579b7d5e40880c75705c8a71.woff   20.8 KiB          [emitted]
ui_1             |             cf6613d1adf490972c557a8e318e0868.woff   19.4 KiB          [emitted]
ui_1             |            19b7a0adfdd4f808b53af7e2ce2ad4e5.woff2     15 KiB          [emitted]
ui_1             |                                       favicon.ico   5.27 KiB          [emitted]
ui_1             |            510dec37fa69fba39593e01a469ee018.woff2   16.5 KiB          [emitted]
ui_1             |            d69924b98acd849cdeba9fbff3f88ea6.woff2   16.7 KiB          [emitted]
ui_1             |            010c1aeee3c6d1cbb1d5761d80353823.woff2   16.2 KiB          [emitted]
ui_1             |             8c2ade503b34e31430d6c98aa29a52a3.woff   19.5 KiB          [emitted]
ui_1             |            d8bcbe724fd6f4ba44d0ee6a2675890f.woff2   16.5 KiB          [emitted]
ui_1             |            55536c8e9e9a532651e3cf374f290ea3.woff2   15.1 KiB          [emitted]
ui_1             |            037d830416495def72b7881024c14b7b.woff2   15.1 KiB          [emitted]
ui_1             |             846d1890aee87fde5d8ced8eba360c3a.woff   20.6 KiB          [emitted]
ui_1             |            987b84570ea69ee660455b8d5e91f5f1.woff2     15 KiB          [emitted]
ui_1             |             bc833e725c137257c2c42a789845d82f.woff   21.3 KiB          [emitted]
ui_1             |             a1471d1d6431c893582a5f6a250db3f9.woff   19.4 KiB          [emitted]
ui_1             |                   0.57f9bbe85e5c6a589b06.chunk.js   26.4 KiB       0  [emitted]
ui_1             |                   1.5783e42c38b5d2362458.chunk.js   35.9 KiB       1  [emitted]
ui_1             |                   2.fd6b8d422b6591d778d4.chunk.js   19.4 KiB       2  [emitted]
ui_1             |                   3.97cde26a7e4a8beb16fa.chunk.js   35.6 KiB       3  [emitted]
ui_1             |                   4.66343c52c02b2ac1456e.chunk.js   74.1 KiB       4  [emitted]
ui_1             |                   5.403fe9d67072167c04b3.chunk.js    135 KiB       5  [emitted]
ui_1             |             210a7c781f5a354a0e4985656ab456d9.woff   21.3 KiB          [emitted]
ui_1             |                   7.d9afb114dfe26231ad65.chunk.js   15.8 KiB       7  [emitted]
ui_1             |                   8.ce827b4d6d0145e15992.chunk.js   11.8 KiB       8  [emitted]
ui_1             |                   9.4afa6b54e754c5e06bbd.chunk.js    106 KiB       9  [emitted]
ui_1             |                  10.809238302226ad749461.chunk.js    142 KiB   10, 2  [emitted]
ui_1             |                  11.9f4f5a15096abbec0859.chunk.js   21.9 KiB      11  [emitted]
ui_1             |                  12.a090991a5f020e5fde7d.chunk.js   44.3 KiB      12  [emitted]
ui_1             |                  13.e16e8381b0ea8c4901ee.chunk.js   68.6 KiB      13  [emitted]
ui_1             |                  14.f958e1dc35ad6b2f22a8.chunk.js   96.3 KiB      14  [emitted]
ui_1             |                  15.cd182d20d490a54f8957.chunk.js   9.53 KiB      15  [emitted]
ui_1             |                  16.5b82e9c566e938020bbd.chunk.js   7.78 KiB      16  [emitted]
ui_1             |                  17.03eff918c86d55d6377b.chunk.js   61.1 KiB      17  [emitted]
ui_1             |                  18.ce425ed211028e9f2163.chunk.js   59.6 KiB      18  [emitted]
ui_1             |                  19.07e7abf3c4eed4b92794.chunk.js   23.6 KiB      19  [emitted]
ui_1             |                  20.764e4d8195ff756292f4.chunk.js   79 bytes      20  [emitted]
ui_1             |              runtime~main.40dc33aa369c965490e3.js   2.69 KiB      21  [emitted]         runtime~main
ui_1             |        vendors~main.fbad551de73a3d110d78.chunk.js    1.6 MiB      22  [emitted]  [big]  vendors~main
ui_1             |                main.c636e3c573fa6f0f0ce9.chunk.js    286 KiB      23  [emitted]         main
ui_1             |                                        index.html  986 bytes          [emitted]
ui_1             |                                             sw.js   22.2 KiB          [emitted]
ui_1             |    manifest.d8fcf0a94683656d7419d47d36076fa6.json   1.67 KiB          [emitted]
ui_1             | icon_512x512.4751ce58b25e8811771c200d23671e91.png   12.4 KiB          [emitted]
ui_1             | icon_384x384.edfa9cacb9b1a25f070a968449102119.png    8.3 KiB          [emitted]
ui_1             | icon_192x192.a850b490191d979987e953b545bff9a6.png    3.2 KiB          [emitted]
ui_1             | icon_180x180.6a2c67316019ef8feaff1fcf98f2c6d3.png   2.91 KiB          [emitted]
ui_1             | icon_167x167.cfc4878a083407e4884b69a80b505731.png   2.75 KiB          [emitted]
ui_1             | icon_152x152.face1ca585254b54b75b9df9c400afc3.png   2.43 KiB          [emitted]
ui_1             | icon_144x144.6a14edf6ded92e6456504b54ea3c85c9.png   2.32 KiB          [emitted]
ui_1             | icon_128x128.b8191e3d81f53d4310e0f543873f6522.png   2.04 KiB          [emitted]
ui_1             | icon_120x120.a7d89eda1a1ea79d0a8e43ed215ffe42.png    1.9 KiB          [emitted]
ui_1             |   icon_96x96.162cc35d3689e3134773f4f70e983d43.png    1.5 KiB          [emitted]
ui_1             |   icon_72x72.f8aa4cce7e8c3451e0a5edcddfc56011.png   1.19 KiB          [emitted]
ui_1             | Entrypoint main [big] = runtime~main.40dc33aa369c965490e3.js vendors~main.fbad551de73a3d110d78.chunk.js main.c636e3c573fa6f0f0ce9.chunk.js
ui_1             | [0785de3f40b134973d35] ./app/i18n.js 2.27 KiB {23} [built]
ui_1             | [1283171292070762fea8] ./app/configureStore.js 3.32 KiB {23} [built]
ui_1             | [63f14ac74ce296f77f4d] ./node_modules/react-dom/index.js 1.33 KiB {22} [built]
ui_1             | [6c925591d78ad1124781] ./app/containers/App/index.js 15.9 KiB {23} [built]
ui_1             | [6cbaae35658a59059130] ./app/containers/LanguageProvider/index.js 7.05 KiB {23} [built]
ui_1             | [1] multi ./app/app.js 28 bytes {23} [built]
ui_1             | [7fa3d1d0596e1f2a0f74] ./app/global-styles.js 52 bytes {23} [built]
ui_1             | [8af190b70a6bc55c6f1b] ./node_modules/react/index.js 190 bytes {22} [built]
ui_1             | [8b703812aa8ae3c41814] ./app/app.js 8.94 KiB {23} [built]
ui_1             | [97694e21b72f8e9351c4] ./node_modules/intl/index.js 574 bytes {6} [built]
ui_1             | [9c6be9f00377ac8be3d8] ./node_modules/file-loader/dist/cjs.js?name=[name].[ext]!./app/images/favicon.ico 57 bytes {23} [built]
ui_1             | [a26e52c4218006ed1d2f] ./node_modules/babel-polyfill/lib/index.js 833 bytes {22} [built]
ui_1             | [d7dd51e1bf6bfc2c9c3d] ./node_modules/react-redux/lib/index.js 751 bytes {22} [built]
ui_1             | [f030ad8f70186ef5cb63] ./node_modules/intl/locale-data/jsonp/en.js 23.5 KiB {19} [built]
ui_1             | [f80cfb70fdcfc87cd982]<EMAIL_ADDRESS>365 bytes {22} [built]
ui_1             |     + 1552 hidden modules
ui_1             |
ui_1             | WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
ui_1             | This can impact web performance.
ui_1             | Assets:
ui_1             |   vendors~main.fbad551de73a3d110d78.chunk.js (1.6 MiB)
ui_1             |
ui_1             | WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
ui_1             | Entrypoints:
ui_1             |   main (1.6 MiB)
ui_1             |       runtime~main.40dc33aa369c965490e3.js
ui_1             |       vendors~main.fbad551de73a3d110d78.chunk.js
ui_1             |
ui_1             | Child __offline_serviceworker:
ui_1             |                       Asset      Size  Chunks  Chunk Names
ui_1             |     __offline_serviceworker  16.1 KiB       0  __offline_serviceworker
ui_1             |     Entrypoint __offline_serviceworker = __offline_serviceworker
ui_1             |     [1f528958a29eea1e7233] ./node_modules/exports-loader?self.fetch!./node_modules/whatwg-fetch/dist/fetch.umd.js 14.5 KiB {0} [built]
ui_1             |     [22249e1ea7baa06e7c1b] ./node_modules/offline-plugin/lib/misc/sw-loader.js?json=%7B%22data_var_name%22%3A%22__wpo%22%2C%22cacheMaps%22%3A%5B%7B%22match%22%3A%22function%28url%29%20%7B%5Cn%20%20%20%20%20%20%20%20%20%20if%20%28url.pathname%20%3D%3D%3D%20location.pathname%29%20%7B%5Cn%20%20%20%20%20%20%20%20%20%20%20%20return%3B%5Cn%20%20%20%20%20%20%20%20%20%20%7D%5Cn%5Cn%20%20%20%20%20%20%20%20%20%20return%20new%20URL%28%5C%22/%5C%22%2C%20location%29%3B%5Cn%20%20%20%20%20%20%20%20%7D%22%2C%22to%22%3Anull%2C%22requestTypes%22%3A%5B%22navigate%22%5D%7D%5D%2C%22navigationPreload%22%3A%22false%22%7D!./node_modules/offline-plugin/tpls/empty-entry.js 21.2 KiB {0} [built]
ui_1             |     [6872a71ed75a597694c7] ./node_modules/offline-plugin/tpls/empty-entry.js 0 bytes {0} [built]
ui_1             | Child html-webpack-plugin for "index.html":
ui_1             |          Asset      Size  Chunks  Chunk Names
ui_1             |     index.html  4.86 KiB       0
ui_1             |     Entrypoint undefined = index.html
ui_1             |     [798c46fd90a016ad8d48] ./node_modules/html-webpack-plugin/lib/loader.js!./app/index.html 1.21 KiB {0} [built]
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
elasticsearch_1  | [2019-05-28T14:52:12,324][WARN ][o.e.d.c.m.MetaDataCreateIndexService] [hoRa3X6] the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template
elasticsearch_1  | [2019-05-28T14:52:12,790][INFO ][o.e.c.m.MetaDataCreateIndexService] [hoRa3X6] [document] creating index, cause [api], templates [], shards [5]/[1], mappings []
elasticsearch_1  | [2019-05-28T14:52:18,315][INFO ][o.e.c.m.MetaDataMappingService] [hoRa3X6] [document/2H0G6BLXQGG2hr4kQEJ17Q] create_mapping [document]
ui_1             | [WS] Connected to http://api:7500

Have you tried going to localhost:8080 ?
https://samtecspg.github.io/articulate/#/getting-started/basic-installation.md#get-it-running

I got it running now.
Thank you so much.....


2GB overhead for VMs

hot fix: Default VM RAM is set to 2GB's but could pose limitations if you want a bigger cluster

nodes require 2GBs of RAM to work with a simple web app on K8s with 1.75GB gemini will complete its install, but paging errors arise when I tried starting a simple web app. https://gist.github.com/danehans/cb744bd10084175ccc44
With 1.5GB of RAM. Gemini will fail during its install, probably on download / extraction of a tar.

@stephenrlouie is this still an issue? What needs to be done, update docs or something else?

We don't have to call this an issue, its just a note. The default Memory size is set to 2GB right now, and it works.

We don't have to call this an issue, its just a note. The default Memory size is set to 2GB right now, and it works.


Angular Cache with Angular 2

Can angular-cache be used with Angular 2? Are there any examples by any chance? Thank you.

Duplicate of #222

My appologies. Not sure how I missed that. Thank you.


Remove unnecesary files from bundled vsix

Remove media/scripts/linter files from the extension. .vsix size 25Mb => 150Kb.

Thank you for your contribution! :D


Store the length of Args when a -- is found in commandline

This allows a program to know what args came before the -- and what args
came after.

I know it's a long time since this was merged, but this was useful to me today, so I wanted to say thank you!


How data is fetched using api?

We use a network call to get data as JSON. JSON is parsed on the client-side.
Does this help?


reevaluate ECR

i originally switched from dockerhub to public ecr because i thought that ecr was a requirement for using aws ecs, but i heard in a random youtube video that ecs actually works fine with public dockerhub. public ecr was kind of a pain to set up, but is working fine. it is less free than public dockerhub, though. at some point in the future (maybe once i'm no longer eligible for aws free tier) i should take another look and decide whether to stay on public ecr or whether to move back to dockerhub.

(honestly i'll probably move off of aws entirely once my free tier expires in late july 2022, because my aws setup will probably cost me ~$400/year and that's kinda nutty when i already have a spare linode)


mpvScripts.mpv-youtube-chat: init at unstable-2023-08-31

Description of changes
Package of mpv script: https://github.com/BanchouBoo/mpv-youtube-chat
Fixes #264549
cc @l0b0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Thank you for the review @eclairevoyant. I incorporated your suggestions.

@FliegendeWurst i'm happy to test & merge this for you if you get a chance to address the feedback above

tested with:
$ nix-shell -p 'mpv.override { scripts = [ mpvScripts.youtube-chat ]; }' --command "mpv https://www.youtube.com/watch?v=Ach8lgF6-AY"

then hit ` and type script-binding load-chat, you should see a diagnostic message and a few seconds later it'll render chat messages in the bottom of the window.
worked for me after applying the feedback above. @nbraud can you unblock?

@nbraud merging is blocked on you: can you please review the latest changes here and update your PR review?


Question:  How can i create action links or buttons as a derived field?

How can i create action links or buttons as a derived field?
I want to introduce either tooltips or action links/buttons on a derived column to lazy load additional information from a backend.  Any HTML i generate using a deriver function seems to be getting encoded and showing up as-is on the column.
how can i achieve this?  Do i have to create a custom renderer and if yes, can i see an example for a jump start?
EDIT: for now i have hacked pivot.js so that
th.textContent = txt;
conditionally becomes
th.innerHTML = txt.html();
works but breaks my build as im using grunt/bower and i have changed in bower_components which is not a version controlled folder.
EDIT2: could not make this work in the above stated method as im using these actions with an angular controller.  So i was forced to make 2 changes..
my derivedAttribute function has to pass the jquery object through a $compile pipe to bind ng-click
$compile($(""))
in pivot.js,
angular.element(th).append(txt); // instead of th.textContent = txt; approx line 850
While all of this works, it takes much longer for my pivot table to load.  My intention is to load modal dialogs on click...
any suggestions on how best to deal with this?  is there an easier/cleaner way of accomplishing this without impacting performance?

My recommendation would be to decorate the table output using jQuery and the onRefresh callback.

I sorted out this issue with a slightly different approach.  i removed $compile and created some indirection.. instead of ng-click i simply called onclick and forward request to controller using a scope handle..

Great!


Transferring transferables to the new thread

I haven't been able to find a path that would allow me to do that

Because the worker messaging API is utilized for thread initialization and termination, there isn't currently a way to send transferables to another thread. The wasm_thread crate would need to be modified to allow for user-generated messages to be posted across worker boundaries, and also allow for asynchronous entrypoints as mentioned in #6. This is possible, but in my view, not necessarily in keeping with the goal of the crate (which is to be a drop-in replacement for std::thread); such functionality would require adding WASM-specific details to the abstraction. It's totally up to the crate owner, of course, but I think it would probably be worth creating a separate crate with webworker-specific functionality (like async entrypoints and the postMessage API) to allow for these advanced worker use cases.

Yes, implementing async entry points and message posting would deviate too far from std::thread API. If we were to implement such features, I think creating a separate crate is the best option. Most of the resuable code could be moved out of this crate and it would instead serve as an API bridge between std::thread and the new webworker-specific crate.
Unfortunatelly, I'm not currently working with wasm so I don't have any interest in implementing this, but I would be happy to accept PRs, help coordinate the effort, or just grant maintainer rights.


User is not available right after login

Hi,
When using angular-permission on the page displayed right after the login process, the user (Authentication.user) is not defined which causes the permission check to fail.
Is there any way to achieve the following?
authentication client controller
$scope.homeUrl = function () {
            $scope.signup = function () {
            $http.post('/auth/signup', $scope.credentials).success(function (response) {
                // If successful we assign the response to the global user model
                $scope.authentication.user = response;

                // And redirect to the index page
                $location.path('/myProtectedUrl');
            }).error(function (response) {
                $scope.error = response.message;
            });
        };

somewhere else in another module
angular.module('dashboard').run(['$rootScope', 'Permission', 'Authentication',
    // Definition of the roles used by the app router
    function ($rootScope, Permission, Authentication) {
        var user = Authentication.user;
        // HERE MY USER IS ALWAYS EMPTY
        Permission.('anonymous', function ($stateParams) {
                return (user === null);
            });
    }]);

BTW, I'm using the mean stack.
Thanks for your help!
tim

Hi,
It seems that I have to retrieve the Authentication provider in my Permission Role Callback to get its value, else I always receive an empty User object as the
var user = Authentication.user

on the 4th line seems to be called only once.
Here is my final code if anyone is interested
.run(['Permission', 'Authentication',
    // Definition of the roles used by the app router
    function (Permission, Authentication) {
        Permission
            .defineRole('anonymous', function ($stateParams) {
                return (Authentication.user === null);
            });
    }]);

Yup, this is because you were assigning null to your user var.
The other solution is to make user an object in the first place and update the object. But the solution to your own problem is the right way to go.
Closing this because it's an application issue and not Permission's.
Cheers


Render stats in footer?

Is there a way to render the statistics in the footer or header templates?
If there are 77 matches but we have set a limit of 10, I'd like to make the footer template say something like "Showing 10 of 77"
Is there a way to do this?  If not, is there any reason I shouldn't add this functionality to the library?

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature

+1 for this feature


New Doc Request -- Telegraf Kafka Consumer Plugin

Need documentation added for the Kafka Consumer Plugin.  There are docs for the output plugin but not the input plugin.
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/kafka_consumer

Doc for this is linked under the Service Inputs
see:

Is this sufficient?

Perfect thank you.


Cannot manage DS records in the portal

Describe the bug
DS records appear in the portal if they exist, but one cannot create, update, or delete them
VinylDNS Version
0.9.0
Expected behavior

I can create, update, or delete a DS record set

@pauljamescleary would this be better classified as a feature request?

I understand we pushed this off for other priorities, but now it is inconsistent and since we have other VinylDNS users these days I am going to keep it as a bug.  Should be a small fix we can get in as part of our normal bug squashing.


Add default prometheus annotations

The static manifests don't configure Policy Reporter with the annotations required for a default helm installed Prometheus to scrape metrics. This PR adds those annotations so Prometheus automatically finds the Policy Reporter pod as a scrape target:

I also noted the default helm install has metrics disabled and the template has support for users to set their own pod annotations.

thanks for your contribution


IoC Services

Right now, the only system with an IoC container is the API system.
When the messaging & scheduling systems are completed, these will require injectable services aswell.
These should be shared between all three of these systems, instead of being defined in each one.
Abstract these out into a new services registry and ensure that the same IoC container can be used in each place. Ensure there is a simple lifecycle - like the current API IoC container.

Added in commit 0f69d9c5ba1fe82fae98e50c82794c91fe096cb0


Update cognitive services parent POM to track 1 parent

This PR updates the parent POM that we are using for all the cognitive services libraries so that they correctly produce artifacts. I'm also updating the version number of all the packages to an unreleased version since this will undoubtedly result dependency changes being inherited.

/azp run java - cognitiveservices - ci


.NET 3.1 installation fails

When I open vscode from WSL, I get this error:
Downloading the .NET Runtime.
Downloading .NET version(s) 3.1.18 ... Error!
Failed to download .NET 3.1.18:
Command failed: "/home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh" -InstallDir "/home/shaunm/.vscode-server-insiders/data/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/3.1.18" -Version 3.1.18 -Runtime dotnet
/home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh: 7: /home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh: Syntax error: newline unexpected
Error!
.NET Acquisition Failed: Installation failed: Error: Command failed: "/home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh" -InstallDir "/home/shaunm/.vscode-server-insiders/data/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/3.1.18" -Version 3.1.18 -Runtime dotnet
/home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh: 7: /home/shaunm/.vscode-server-insiders/extensions/ms-dotnettools.vscode-dotnet-runtime-1.2.0/dist/install scripts/dotnet-install.sh: Syntax error: newline unexpected
This is coming from .NET Install Tool for Extension Authors which Visual Studio IntelliCode Insiders depends upon.
I cannot uninstall the .NET extension because Intellicode depends on it.
Product and Version [VS/VSCode]:
Version: 1.61.0-insider (user setup)
Commit: ec40cbe164c59f3d13b6eff5fc7b0231ec0ab7aa
Date: 2021-09-13T05:15:14.689Z (20 hrs ago)
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
IntelliCode Extension Version:
Visual Studio IntelliCode Insiders v1.1.4
Steps to Reproduce / Scenario:

From a WSL terminal: code-insiders .

The new version of '.NET Install Tool for Extension Authors' has been released and it fixes issue. Let me know if you still see the issue(you might need to uninstall '.NET Install Tool for Extension Authors' to get rid of cache issue).

I uninstalled the retail Intellicode and installed IntelliCode Insiders for WSL. I got the same dotnet installation error. Interestingly, Intellicode Insiders thinks it is installed. I can hover and see examples on GitHub, so it must be installed and working. Maybe the error was left over from a previously installed extension; I'm not sure.
I tried installing on another machine. That machine received no error. So it appears that the error has been fixed.


Awake keeps monitors on even if "Keep monitors on" is unchecked

Microsoft PowerToys version
v0.62.0
Running as admin

[ ] Yes

Area(s) with issue?
Awake
Steps to reproduce
Turn on Awake (Keep on indefinitely).
Let PC lock.
Monitors do not turn off.
✔ Expected Behavior
Monitors should go to sleep as usual, while computer does not sleep.
❌ Actual Behavior
Monitors stay awake after locking/idle, and do not go into standby.
Other Software
No response

Should be fixed with the latest releases.


Removes all upper bounds on dependencies and run constrained.

symmeplot is not easily installable into environments with other packages due to unnecessary upper bounds placed on the dependencies, so all have been removed
matplotlib was added as the default backend, because symmeplot does not work otherwise, if a backend-free package is needed then a symmeplot-core and symmeplot should be created much like matplotlib-base and matplotlib
pyqt6 does not exist as a package in conda-forge, so removed
all run_constrained items are removed, if a user wants to use the other backends they can install them with conda install pyqt>=6.0 as per symmeplot instructions

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


MQTT Forwarder request for MikroTik

Hello,
this is a request for an MQTT forwarder to suit the MikroTik Gateways please.
Specifically RBwAPR-2nD_R11e-LoRa9
Thanks

Hi Orne,
ok thanks, please let me check with MikroTik and my distributor. I do know they have on some of their routerOS v7 and above  the ability to host Docker but will see if the LoRa specific Gateways can do this.
I thought you can SSH into it but let me report back .
Cheers

Do you have any update on this? Else I will close this issue.

Hi Orne,
Apologies for the delay in getting back to this,
Theres also the  ability with v7 to run docker containers, just not sure on if there's enough disk on MikroTik WAP8 or WAP9.
https://help.mikrotik.com/docs/display/ROS/Container
RouterOS only has built-in MQTT functionality using:
https://help.mikrotik.com/docs/display/ROS/MQTT

Container package is compatible with arm arm64 and x86 architectures. Using of remote-image (similar to docker pull) functionality requires a lot of free space in main memory, 16MB SPI flash boards may use pre-build images on USB or other disk media.

The WAP8 and WAP9 are MIPS, so I don't think this will be an option.

Thanks Orne!
no problem, we got basic station working on it instead. So you can close this issue.
Also regarding ssh on how into MikroTik I have attached the CLI

Also regarding ssh on how into MikroTik I have attached the CLI

I also managed to SSH into the gateway before, but it only provided me with a CLI shell to configure MikroTik parameters, eg. I was unable to get access to a bash-like shell where I could execute just any command.


updated bulgarian translation

Coverage remained the same at 100.0% when pulling 006a80ed19340ecd5438b8d5ce8886909ce16a86 on AdmiralAnimE:master into 1dc28777c8ce20dbb88c39f3d1c35517d42118aa on mrdokenny:master.

Thanks! I'll merge this but next time use single quotes since github is showing red on those lines.

Okay, I was wondering what was the problem there.. :)


Cannot upgrade Micronaut from Gradle 4.10 to Gradle 5 or above due to JAR locking

We have been trying for some time now to upgrade to Gradle 5 or 6 and are blocked by an issue where Gradle locks the JAR files for submodules that are also annotation processors meaning if these subprojects are used as an annotation processor other subprojects they cannot be loaded due to Gradle locking them
This results in a core dump unless -Dsun.zip.disableMemoryMapping=true is specified however specifying this results in services not being able to be loaded that the annotation processors require.
Expected Behavior
Gradle should not lock the JAR files of annotation processor projects in subprojects as in Gradle 4.x
Current Behavior
Gradle locks annotation processor subprojects preventing their correct usage in other modules of the same build.
Context
We cannot upgrade the Micronaut core build above Gradle 4.10 and therefore cannot test on JDK 13 or above.
Related PR https://github.com/micronaut-projects/micronaut-core/pull/2128
Steps to Reproduce
git clone https://github.com/zendern/micronaut-core.git
cd micronaut-core
git checkout -b zendern-gradle-upgrade master
git pull https://github.com/zendern/micronaut-core.git gradle-upgrade
./gradlew test

I tried to work around this in this branch by catching the exceptions in loading the services the Micronaut compiler users that are loaded via ServiceLoader and fallbacking back to instantiating them directly:
https://github.com/micronaut-projects/micronaut-core/commit/328f8bb02c29cca4dadbcd90a57b80b6c25f0b4b#diff-8722e88034b196b53ceb5f774c64603eR239
This allows the build to get further but something is still very broken with tests failing with SSL errors. Also if I run
./gradlew test --parallel --continue
The JVM completely crashes unless I add export GRADLE_OPTS="-Dsun.zip.disableMemoryMapping=true
Once I added that and I run ./gradlew test --parallel --continue then compilation errors occur:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=372m; support was removed in 8.0

> Task :core:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :inject:compileJava
error: error reading /Users/graemerocher/dev/micronaut/core/core/build/libs/core-1.3.0.BUILD-SNAPSHOT.jar; error in opening zip file
error: error reading /Users/graemerocher/dev/micronaut/core/core/build/libs/core-1.3.0.BUILD-SNAPSHOT.jar; cannot read zip file
/Users/graemerocher/dev/micronaut/core/inject/src/main/java/io/micronaut/context/AbstractParametrizedBeanDefinition.java:21: error: package io.micronaut.core.annotation does not exist
import io.micronaut.core.annotation.AnnotationMetadata;
                                   ^
/Users/graemerocher/dev/micronaut/core/inject/src/main/java/io/micronaut/context/AbstractParametrizedBeanDefinition.java:22: error: package io.micronaut.core.annotation does not exist
import io.micronaut.core.annotation.Internal;

Note the output that says error reading /Users/graemerocher/dev/micronaut/core/core/build/libs/core-1.3.0.BUILD-SNAPSHOT.jar; error in opening zip file
So it is even locking JAR files produced via compilation somehow.

@graemerocher it looks like there's been some changes since you first opened this.  What's a good commit that reproduces the locking error?  All I can get are compilation errors.
Which version of Java are you using?
Can you describe what you're seeing WRT which jars are being locked and which jars are being modified?  It seems like you're saying the annotation processor jars are being modified by another project?

@big-guy Thanks for the response. Can you try:
git clone https://github.com/micronaut-projects/micronaut-core.git
cd micronaut-core
git checkout zendern-gradle-upgrade
./gradlew clean cJ --no-daemon

You should be output like the following for the runtime subproject:
Failed to configure default AnnotationMappers. Using fallback behaviour: Failed to load resources for service [io.micronaut.inject.annotation.AnnotationMapper]: jar:file:/Users/graemerocher/dev/micronaut/core/inject/build/libs/inject-1.3.0.BUILD-SNAPSHOT.jar!/META-INF/services/io.micronaut.inject.annotation.AnnotationMapper
Failed to configure default AnnotationMappers. Using fallback behaviour: Failed to load resources for service [io.micronaut.inject.annotation.AnnotationRemapper]: jar:file:/Users/graemerocher/dev/micronaut/core/inject/build/libs/inject-1.3.0.BUILD-SNAPSHOT.jar!/META-INF/services/io.micronaut.inject.annotation.AnnotationRemapper
Failed to configure default TypeElementVisitors. Using fallback behaviour: Failed to load resources for service [io.micronaut.inject.visitor.TypeElementVisitor]: jar:file:/Users/graemerocher/dev/micronaut/core/inject/build/libs/inject-1.3.0.BUILD-SNAPSHOT.jar!/META-INF/services/io.micronaut.inject.visitor.TypeElementVisitor

Which is one manifestation of the problem. If you run:
./gradlew clean cJ --parallel --no-daemon

You get compilation errors which are unexpected with the inject project unable to read the classes of the core project even though the jar contains theses classes:
> Task :inject:compileJava
error: error reading /Users/graemerocher/dev/micronaut/core/core/build/libs/core-1.3.0.BUILD-SNAPSHOT.jar; error in opening zip file
error: error reading /Users/graemerocher/dev/micronaut/core/core/build/libs/core-1.3.0.BUILD-SNAPSHOT.jar; cannot read zip file
/Users/graemerocher/dev/micronaut/core/inject/src/main/java/io/micronaut/context/AbstractParametrizedBeanDefinition.java:21: error: package io.micronaut.core.annotation does not exist
import io.micronaut.core.annotation.AnnotationMetadata;
                                   ^

Which version of Java are you using?

We build with JDK 8.

Can you describe what you're seeing WRT which jars are being locked and which jars are being modified? It seems like you're saying the annotation processor jars are being modified by another project?

Let me try and describe the issue better. The micronaut-core project is a multi project build. One of the subprojects is an annotation processor. This is micronaut-inject-java: https://github.com/micronaut-projects/micronaut-core/tree/master/inject-java
The inject-java subproject is placed on the annotation processor classpath of other subprojects. See for example the runtime subproject: https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/runtime/build.gradle#L42
With Gradle 4.10 this was not a problem. But with Gradle 5 and above what happens is that the annotation processor is unable to load, via service loader, files and classes from JARs on the annotation processor classpath since this JARs are locked somehow.
This manifests in a few places that breaks our build. One place is in AbstractAnnotationMetadataBuilder which uses a variation of service loader to load classes of type AnnotationMapper: https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/inject/src/main/java/io/micronaut/inject/annotation/AbstractAnnotationMetadataBuilder.java#L58
In Gradle 4.10 this worked, but in Gradle 5+ this results in a ServiceConfigurationError and I placed a hack to fallback to statically loading this classes instead of dynamically which is here: https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/inject/src/main/java/io/micronaut/inject/annotation/AbstractAnnotationMetadataBuilder.java#L79
You can reproduce this with the following steps. If you uncomment the following lines which allows attaching a remote debugger to Gradle compilation: https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/runtime/build.gradle#L56
Then set a break point on https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/inject/src/main/java/io/micronaut/inject/annotation/AbstractAnnotationMetadataBuilder.java#L58
And run the following command:
./gradlew clean cJ --no-daemon

And attach the debugger you will see that when the runtime project is compiled the annotation processor is able to find the META-INF/services/io.micronaut.inject.annotation.AnnotationMapper files within the JAR files that are on the classpath of the annotation processor, however when it attempts to load any of these files via URL.openStream() the result is a FileNotFoundException which then manifests as the ServiceConfigurationError which then results in output like:
Failed to configure default AnnotationMappers. Using fallback behaviour: Failed to load resources for service [io.micronaut.inject.annotation.AnnotationMapper]: jar:file:/Users/graemerocher/dev/micronaut/core/inject/build/libs/inject-1.3.0.BUILD-SNAPSHOT.jar!/META-INF/services/io.micronaut.inject.annotation.AnnotationMapper

This did not occur in Gradle 4.10 and the reason why it is occuring in Gradle 5+ doesn't make sense to me. It seems that Gradle 5+ is somehow preventing the annotation processor (possibly by not closes a reference to these JAR files) from reading the contents of any JAR file produced by the same build that is on the annotation processor classpath. I hope this serves as a better explanation of the project.
Note that I have tried various things such as removing the usage of shadow JAR (too see if that was the problem) but it does not appear to be.

Thanks for all the details @graemerocher.
It looks like this is being caused by the shadowJar task overwriting the existing jar concurrently to compilation by other projects.  I got a little suspicious when I was able to get successful builds by running fewer tasks or running mostly up-to-date builds.
I then noticed this:
https://scans.gradle.com/s/ues2t7w3x5qe4/timeline?details=65ev7keldv2bw
The shadowJar task was running at the same time as the failing compile task. To dig a little deeper, I disable the shadow task for core and tried again:
https://scans.gradle.com/s/q2skbc6c4anfu/timeline?details=742yun4u67p3c&end=1576046852382&start=1576046851634
In this case, inject compiled fine, but the problem moved to another project that also had another shadowJar running concurrently.
I then checked the configuration of the shadowJar and saw that it was writing to the same location as the regular jar task.  This sounded familiar, so I tried bumping to the latest Shadow plugin (5.2.0), but that didn't fix it.  So I removed this line: https://github.com/micronaut-projects/micronaut-core/blob/zendern-gradle-upgrade/build.gradle#L695 which changed the path to the jar to something else.  I think what may have changed between 4.x and now is how this default value is determined and the shadow plugin is inadvertently using the same as the regular jar task.
This got me through more of the compilation, up to this point:
https://scans.gradle.com/s/wjmassgsie726/failure?openFailures=WzBd&openStackTraces=WzNd#top=0
This looks like a mismatch between something expecting the shaded version of ASM and getting the non-shaded version.  Does this ring any bells?

@lptr is this something we could detect somehow?  e.g., if a task declares that it writes to a file that's an input to an executing task, we should warn/fail because this means something is wrong.  That could be a missing dependency or two tasks overwriting their outputs (like in this case)

@big-guy That would be an indication that classes have been rewritten to use the shaded version of ASM but the core module which contains these shaded versions hasn't been rewritten and therefore those classes are not the classpath

@big-guy we don't do checks like that yet. The plan for next year is add validation to the task graph, so if a task uses a (part of the) output produced by another task, then there has to be a build dependency between them. That should cover the use case you mentioned.

@big-guy Thanks for sending me in the right direction. I have managed to progress the upgrade further. I have no idea how you were able to discover the cause, I guess one needs to be an expert on Gradle internals to figure out these things.
however I am now quite frequently hitting https://github.com/gradle/gradle/issues/10985 which results in the need for a full recompilation. One comment on that issue says it is fixed in 6.0.1 but that does not appear to be the case for me.

I have no idea how you were able to discover the cause, I guess one needs to be an expert on Gradle internals to figure out these things.

The symptoms looked like something was "corrupting" the jar during compilation.  I've been burned by that before (outside Gradle).  The timeline in https://scans.gradle.com/s/ues2t7w3x5qe4/timeline?details=qalcau5375bxi made me look at core:shadowJar first:

I posted a comment with a nightly to try for your other issue.  I'll close this issue for now.


Add Security Headers

This Pull Request adds the following HTTP Security Headers to TorPaste:

X-Frame-Options
X-Xss-Protection
X-Content-Type-Options
Content-Security-Policy

@j11e Can you verify everything's okay with this PR? I checked using pep8 in terminal but a code review wouldn't hurt.. :-)

Changes are ok with me!


refactor(speaker-list): change call clipboard to ionic-native

Related #252

Close to submit in master


Tab characters in the markdown

At the time of writing there are 29 tab characters spread across the files: delegates.md, documentation-comments.md, enums.md and expressions.md. Many, but not all, are in code blocks and may exist due to copy’n’paste. They may not produce the expected results, recommend removing them.
Note: Some of these were discovered while processing the markdown, they broke the markdown parser (Markdig) in use…

Absolutely agree. I thought I'd removed them all recently, but either my memory is failing me or my tooling is!

Maybe it’s my copy which dates before your fixes. I’ll check tomorrow and close the issue if they’re gone.

On 2/02/2022, at 7:26 pm, Jon Skeet @.***> wrote:
Absolutely agree. I thought I'd removed them all recently, but either my memory is failing me or my tooling is!
—
Reply to this email directly, view it on GitHub https://github.com/dotnet/csharpstandard/issues/450#issuecomment-1027626132, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSYVW73QBO2QG7ZG52OL73UZDE75ANCNFSM5NLBWHFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

This was the commit that removed them:
https://github.com/dotnet/csharpstandard/commit/89f99c9fd0bac4abaa37197670a7e860d3420dab

Jon has fixed them all already, closing with thanks :-)


Question:  Why can't I nest more than 20 documents?

I see that MAX_DEPTH is a constant of 20 in BsonMapper.  Why is this? Is this an arbitrarily chosen number, or is there a technical reason we cannot override this number and set it to say, 40?

Hi @iupchris10, it´s just an arbitrarily number, can be increse to any number.... it´s just to simple way to detect circular reference.

Thanks @mbdavid. That makes sense. It would be a nice enhancement to make this a public property on BsonMapper.cs, with a default setting of 20, rather than a constant.
Keep up the good work. LiteDB is working out great for me so far as a cross-platform doc store.


Dumping JSON for playlists returns invalid syntax

When calling youtube-dl with the --dump-json argument and a playlist, like this:
youtube-dl --dump-json https://www.youtube.com/watch?v=5Fjjgjcvj24&list=PLvMgpveoV8oRvM_kBZULuPn5wlQkUjPth

then it returns invalid json, which looks like that:
{ "upload_date":"20130922", .. } { "upload_date":"20130922", .. } { "upload_date":"20130922", .. }

I can't JSON.parse() it, because first, there is no comma between each element, and second, it has to be an array, so it should like that:
[{ "upload_date":"20130922", .. }, { "upload_date":"20130922", .. }, { "upload_date":"20130922", .. } ]

Or am I just missing something?
I'm using the latest version on npm.
As a workaround, you have to use --dump-single-json or -J to get a correct result.

How about:
string_from_youtube_dl.split('\n').map(JSON.parse)

Given you're using Javascript.

This is expected behavior. --dump-json outputs JSON for each video separately.


companion bugs default https host for nginx proxy

Hi. I noticed that when using companion (separate containers scenario) there are no default.key and default.crt in /etc/nginx/certs/ and that makes nginx.tmpl to not generate a default https (and first) 'server' in configuration that would respond with 503. Because of that, when creating such stack, anyone can query my server on https by ip and nginx will respond with first valid https configuration, and not 503 like it should. How can we fix this?
Steps to reproduce:
Start 3 separate containers like in readme: https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/blob/master/README.md#separate-containers.
Then start a whoami container:
sudo docker run -d --name whoami -h whoami -e VIRTUAL_HOST=whoami.local -e LETSENCRYPT_HOST=whoami.local -e<EMAIL_ADDRESS>LETSENCRYPT_TEST=true --restart=unless-stopped -i -t -P jwilder/whoami
And reach that server but not by whoami.local, but but localhost or IP Address. It will respond with whoami.local. It works fine on port 80 (responds with 503), but on 443 it will load whoami server.

Hi.
Correct me if I'm wrong, but I think the same thing would happen even if one does not use letsencrypt-nginx-proxy-companion at all and just manually put certificates on the /etc/nginx/certs folder as described in the nginx-proxy doc.

Yeah, I think You are right. Today I figured out how to setup this correctly, although it would be nice to have this information in readme or somewhere.
So basically I change my claim on this issue from "Bug" to "Needs more information in Readme"

I guess my issue #411 is describing the same thing, but I am not sure if we should simply document this and call it a day.
Making up some invalid placeholder certs for default doesn't quite make sense in production.
I see that users of nginx-proxy is very likely to start without a valid default upstream, and may never will.
How about disabling access to default server in the default template for nginx-proxy and rely solely on VIRTUAL_HOST? Users do need a default upstream can always override it with a separate docker-gen container.


Add transaction::Version data type

BIP-68 activated a fair while ago (circa 2019) and since then only transaction versions 1 and 2 have been considered standard.
Currently in our Transaction struct we use an i32, this means users can construct a non-standard transaction if they do not first look up what the value should be. We can help folk out here by abstracting over the version number.
Add transaction::Version data type that simply provides two consts ONE and TWO.
Add a Default impl on Version that returns Version::TWO.
In tests that used version 0, instead use Version::default because the test obviously does not care.

5ae780682964700dde2cd03c802a12cdf2a9b4d2 looks good except that we should add a constructor for creating arbitrary version numbers. We can comment that there is no reason (on mainnet at least) to use this, but it should be possible.
Alternately we could make the inner i32 public.

Good reviewing lads, thank you. Changes in force push

Make the inner i32 public and document that we do not enforce any invariants on the version number.
Add non_standard constructor
Add is_standard (eg, in case folk want to check after decoding)

Thanks for merging @clarkmoody!
In future though could you use the Bitcoin Core merge script (it is not actually Core-specific at all). It creates a more uniform merge commit message, gpg-signs the merge commits, does a few sanity checks, and looks for ACKs in the PR comments.

Thanks for merging @clarkmoody!
In future though could you use the Bitcoin Core merge script (it is not actually Core-specific at all). It creates a more uniform merge commit message, gpg-signs the merge commits, does a few sanity checks, and looks for ACKs in the PR comments.

Oops! Will use that script for future merges.

Clearly a sacking offence, @clarkmoody please step down and return all salary payments already received ;)


Create utility to provide context/scope for translation ids

On the server there is the ability to pass in a scope for an id which enables the caller to build up the key piece by piece. (development handbook link)
For instance, to build the id a.b.c.d you can:
    I18n.t(
      'd',
      scope: ['a', 'b', 'c'],
      substitution1: 'some_value',
      substitution2: 'another_value',
    )

It would be useful if the client-side libraries allowed the user to pass in a scope array rather than having to build it manually before calling the translate() function.
Moved from https://github.com/Shopify/web/issues/5525.

This one is implemented in the react-i18n library once it is moved in: https://github.com/Shopify/quilt/pull/238

Closing via #238