text:
LogStash exiting with Code 1

Hi , I am facing issues starting up the logstash. I have checked a similar issue that someone else asked and tried that solution as well, still no luck. The logstash container starts and shuts down within 2 minutes with the below error; Also I do not see logstash, elasticsearch and kibana in /etc and /var directories. Can you please help.
logstash_1       | Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties.
dockerelk_logstash_1 exited with code 1
Below is the docker-compose.yml
version: '2'

services:
  elasticsearch:
    build: elasticsearch/
    ports:
      - "9200:9200"
      - "9300:9300"
    environment:
      ES_JAVA_OPTS: "-Xms1g -Xmx1g"
    networks:
      - docker_elk
  logstash:
    build: logstash/
    command: -f /etc/logstash/conf.d/
    volumes:
      - ./logstash/config:/etc/logstash/conf.d
    ports:
      - "5000:5000"
    networks:
      - docker_elk
    environment:
      - LS_HEAP_SIZE=1g
  kibana:
    build: kibana/
    volumes:
      - ./kibana/config/:/opt/kibana/config/
    ports:
      - "5601:5601"
    networks:
      - docker_elk

networks:
  docker_elk:
    driver: bridge

And logstash.conf
input {
  tcp {
    port => 5000
    data_timeout => 600
  }
}
filter {
    mutate {
      strip => "message"
    }
    grok {   ..........
........................
   }

    kv {
      field_split => "&"
      source => payload
    }
    mutate {
      convert => ["T", "float"]
            remove_field =>  ["garbage", "dt_year", "dt_month",  "dt_day", "dt_hour", "dt_minute", "dt_second", "payload", "message", "CALTYPE", "FREE_MEM"]
    }
}
output {
        elasticsearch {
                host => localhost
                port => 9200
                index => "logstash-%{+YYYY.MM.dd}"
        }
}

Kernel Info:
3.13.0-46-generic #77-Ubuntu
Docker Engine:
 docker-engine:
  Installed: 1.12.3-0~trusty
  Candidate: 1.12.3-0~trusty
  Version table:
 *** 1.12.3-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
        100 /var/lib/dpkg/status
     1.12.2-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.12.1-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.12.0-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.11.2-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.11.1-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.11.0-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.10.3-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
     1.10.2-0~trusty 0
        500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages

Could you copy the logs of docker-compose up here too please?

Attaching to dockerelk_logstash_1, dockerelk_elasticsearch_1, dockerelk_kibana_1
logstash_1       | Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties.
elasticsearch_1  | [2016-11-22T22:55:12,613][INFO ][o.e.n.Node               ] [] initializing ...
elasticsearch_1  | [2016-11-22T22:55:13,054][INFO ][o.e.e.NodeEnvironment    ] [uZAk4ml] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/disk/by-uuid/21813bed-571e-4fcc-905d-32bc13641493)]], net usable_space [14.5gb], net total_space [29.4gb], spins? [possibly], types [ext4]
elasticsearch_1  | [2016-11-22T22:55:13,059][INFO ][o.e.e.NodeEnvironment    ] [uZAk4ml] heap size [1007.3mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2016-11-22T22:55:13,067][INFO ][o.e.n.Node               ] [uZAk4ml] node name [uZAk4ml] derived from node ID; set [node.name] to override
elasticsearch_1  | [2016-11-22T22:55:13,076][INFO ][o.e.n.Node               ] [uZAk4ml] version[5.0.0], pid[1], build[253032b/2016-10-26T05:11:34.737Z], OS[Linux/3.13.0-46-generic/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_111/25.111-b14]
elasticsearch_1  | [2016-11-22T22:55:20,846][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [ingest-common]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-expression]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-groovy]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-mustache]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-painless]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [percolator]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [reindex]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [transport-netty3]
elasticsearch_1  | [2016-11-22T22:55:20,851][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [transport-netty4]
elasticsearch_1  | [2016-11-22T22:55:20,859][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded plugin [x-pack]
elasticsearch_1  | [2016-11-22T22:55:23,386][WARN ][o.e.d.s.g.GroovyScriptEngineService] [groovy] scripts are deprecated, use [painless] scripts instead
elasticsearch_1  | [2016-11-22T22:55:33,357][INFO ][o.e.n.Node               ] [uZAk4ml] initialized
elasticsearch_1  | [2016-11-22T22:55:33,357][INFO ][o.e.n.Node               ] [uZAk4ml] starting ...
elasticsearch_1  | [2016-11-22T22:55:34,542][INFO ][o.e.t.TransportService   ] [uZAk4ml] publish_address {172.18.0.4:9300}, bound_addresses {[::]:9300}
elasticsearch_1  | [2016-11-22T22:55:34,565][INFO ][o.e.b.BootstrapCheck     ] [uZAk4ml] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
elasticsearch_1  | ERROR: bootstrap checks failed
elasticsearch_1  | max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
elasticsearch_1  | [2016-11-22T22:55:34,600][INFO ][o.e.n.Node               ] [uZAk4ml] stopping ...
elasticsearch_1  | [2016-11-22T22:55:34,741][INFO ][o.e.n.Node               ] [uZAk4ml] stopped
elasticsearch_1  | [2016-11-22T22:55:34,741][INFO ][o.e.n.Node               ] [uZAk4ml] closing ...
elasticsearch_1  | [2016-11-22T22:55:34,810][INFO ][o.e.n.Node               ] [uZAk4ml] closed
elasticsearch_1  | [2016-11-22T22:58:27,371][INFO ][o.e.n.Node               ] [] initializing ...
elasticsearch_1  | [2016-11-22T22:58:27,569][INFO ][o.e.e.NodeEnvironment    ] [uZAk4ml] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/disk/by-uuid/21813bed-571e-4fcc-905d-32bc13641493)]], net usable_space [14.6gb], net total_space [29.4gb], spins? [possibly], types [ext4]
elasticsearch_1  | [2016-11-22T22:58:27,570][INFO ][o.e.e.NodeEnvironment    ] [uZAk4ml] heap size [1007.3mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2016-11-22T22:58:27,574][INFO ][o.e.n.Node               ] [uZAk4ml] node name [uZAk4ml] derived from node ID; set [node.name] to override
elasticsearch_1  | [2016-11-22T22:58:27,580][INFO ][o.e.n.Node               ] [uZAk4ml] version[5.0.0], pid[1], build[253032b/2016-10-26T05:11:34.737Z], OS[Linux/3.13.0-46-generic/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_111/25.111-b14]
elasticsearch_1  | [2016-11-22T22:58:34,022][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2016-11-22T22:58:34,023][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [ingest-common]
elasticsearch_1  | [2016-11-22T22:58:34,023][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-expression]
elasticsearch_1  | [2016-11-22T22:58:34,024][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-groovy]
elasticsearch_1  | [2016-11-22T22:58:34,024][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-mustache]
elasticsearch_1  | [2016-11-22T22:58:34,024][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [lang-painless]
elasticsearch_1  | [2016-11-22T22:58:34,025][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [percolator]
elasticsearch_1  | [2016-11-22T22:58:34,025][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [reindex]
elasticsearch_1  | [2016-11-22T22:58:34,025][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [transport-netty3]
elasticsearch_1  | [2016-11-22T22:58:34,026][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded module [transport-netty4]
elasticsearch_1  | [2016-11-22T22:58:34,031][INFO ][o.e.p.PluginsService     ] [uZAk4ml] loaded plugin [x-pack]
elasticsearch_1  | [2016-11-22T22:58:35,393][WARN ][o.e.d.s.g.GroovyScriptEngineService] [groovy] scripts are deprecated, use [painless] scripts instead
kibana_1         | Stalling for Elasticsearch
kibana_1         | Stalling for Elasticsearch
elasticsearch_1  | [2016-11-22T22:58:46,030][INFO ][o.e.n.Node               ] [uZAk4ml] initialized
elasticsearch_1  | [2016-11-22T22:58:46,039][INFO ][o.e.n.Node               ] [uZAk4ml] starting ...
elasticsearch_1  | [2016-11-22T22:58:46,798][INFO ][o.e.t.TransportService   ] [uZAk4ml] publish_address {172.18.0.2:9300}, bound_addresses {[::]:9300}
elasticsearch_1  | [2016-11-22T22:58:46,814][INFO ][o.e.b.BootstrapCheck     ] [uZAk4ml] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
elasticsearch_1  | [2016-11-22T22:58:50,270][INFO ][o.e.c.s.ClusterService   ] [uZAk4ml] new_master {uZAk4ml}{uZAk4ml8T5u38pDL9i92ug}{V-jrBUgOTK6x7cO_ut4APw}{172.18.0.2}{172.18.0.2:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
elasticsearch_1  | [2016-11-22T22:58:50,375][INFO ][o.e.h.HttpServer         ] [uZAk4ml] publish_address {172.18.0.2:9200}, bound_addresses {[::]:9200}
elasticsearch_1  | [2016-11-22T22:58:50,375][INFO ][o.e.n.Node               ] [uZAk4ml] started
kibana_1         | Starting Kibana
elasticsearch_1  | [2016-11-22T22:58:50,766][INFO ][o.e.g.GatewayService     ] [uZAk4ml] recovered [0] indices into cluster_state
elasticsearch_1  | [2016-11-22T22:58:53,357][INFO ][o.e.m.j.JvmGcMonitorService] [uZAk4ml] [gc][7] overhead, spent [311ms] collecting in the last [1s]
elasticsearch_1  | [2016-11-22T22:58:56,513][INFO ][o.e.x.m.e.Exporters      ] [uZAk4ml] skipping exporter [default_local] as it isn't ready yet
elasticsearch_1  | [2016-11-22T22:58:56,517][ERROR][o.e.x.m.AgentService     ] [uZAk4ml] exception when exporting documents
elasticsearch_1  | org.elasticsearch.xpack.monitoring.exporter.ExportException: exporters are either not ready or faulty
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:188) ~[x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.AgentService$ExportingWorker.run(AgentService.java:208) [x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:kibana@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:06Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1  | [2016-11-22T22:59:06,789][INFO ][o.e.c.m.MetaDataCreateIndexService] [uZAk4ml] [.monitoring-es-2-2016.11.22] creating index, cause [auto(bulk api)], templates [.monitoring-es-2], shards [1]/[1], mappings [_default_, node, shards, index_stats, index_recovery, cluster_state, cluster_stats, indices_stats, node_stats]
elasticsearch_1  | [2016-11-22T22:59:07,175][INFO ][o.e.c.m.MetaDataCreateIndexService] [uZAk4ml] [.monitoring-data-2] creating index, cause [auto(bulk api)], templates [.monitoring-data-2], shards [1]/[1], mappings [node, kibana, cluster_info]
elasticsearch_1  | [2016-11-22T22:59:07,903][INFO ][o.e.c.m.MetaDataMappingService] [uZAk4ml] [.monitoring-es-2-2016.11.22/IMC9saa4RWWd0YZ3M6LiNQ] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-22T22:59:08,059][INFO ][o.e.c.m.MetaDataMappingService] [uZAk4ml] [.monitoring-es-2-2016.11.22/IMC9saa4RWWd0YZ3M6LiNQ] update_mapping [node_stats]
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:12Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:12Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:12Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:12Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
elasticsearch_1  | [2016-11-22T22:59:12,887][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [buildNum]
elasticsearch_1  | [2016-11-22T22:59:12,891][INFO ][o.e.c.m.MetaDataCreateIndexService] [uZAk4ml] [.kibana] creating index, cause [api], templates [], shards [1]/[1], mappings [server, config]
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch: mode: trial | status: active | expiry date: 2016-12-22T22:58:56+00:00"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from green to yellow - Waiting for Monitoring Health Check","prevState":"green","prevMsg":"Ready"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:13Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:16Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Monitoring Health Check"}
elasticsearch_1  | [2016-11-22T22:59:18,384][INFO ][o.e.c.m.MetaDataMappingService] [uZAk4ml] [.monitoring-es-2-2016.11.22/IMC9saa4RWWd0YZ3M6LiNQ] update_mapping [index_stats]
elasticsearch_1  | [2016-11-22T22:59:18,538][INFO ][o.e.c.m.MetaDataMappingService] [uZAk4ml] [.monitoring-es-2-2016.11.22/IMC9saa4RWWd0YZ3M6LiNQ] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-22T22:59:18,602][INFO ][o.e.c.m.MetaDataMappingService] [uZAk4ml] [.monitoring-es-2-2016.11.22/IMC9saa4RWWd0YZ3M6LiNQ] update_mapping [indices_stats]
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:19Z","tags":["status","plugin:security@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:19Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:19Z","tags":["security","warning"],"pid":1,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:20Z","tags":["status","plugin:console@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:20Z","tags":["status","plugin:timelion@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:20Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0.0.0.0:5601"}
kibana_1         | {"type":"log","@timestamp":"2016-11-22T22:59:20Z","tags":["status","ui settings","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1  | [2016-11-22T22:59:23,622][INFO ][o.e.c.m.MetaDataCreateIndexService] [uZAk4ml] [.monitoring-kibana-2-2016.11.22] creating index, cause [auto(bulk api)], templates [.monitoring-kibana-2], shards [1]/[1], mappings [_default_, kibana_stats]
logstash_1       | Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties.
dockerelk_logstash_1 exited with code 1

Looks like you forgot one part in the setup:
elasticsearch_1  | ERROR: bootstrap checks failed
elasticsearch_1  | max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]

Please read the documentation on how to start the stack: https://github.com/deviantony/docker-elk#increase-max_map_count-on-your-host-linux

Hi @deviantony , I did try that step before starting the containers, not sure why that error occured.
Anyway , I executed that command again and restarted the containers, still the same error;
Attaching to dockerelk_elasticsearch_1, dockerelk_logstash_1, dockerelk_kibana_1
kibana_1         | Stalling for Elasticsearch
elasticsearch_1  | [2016-11-23T00:25:40,123][INFO ][o.e.n.Node               ] [] initializing ...
elasticsearch_1  | [2016-11-23T00:25:40,311][INFO ][o.e.e.NodeEnvironment    ] [NggTRJz] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/disk/by-uuid/21813bed-571e-4fcc-905d-32bc13641493)]], net usable_space [12.7gb], net total_space [29.4gb], spins? [possibly], types [ext4]
elasticsearch_1  | [2016-11-23T00:25:40,313][INFO ][o.e.e.NodeEnvironment    ] [NggTRJz] heap size [1007.3mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2016-11-23T00:25:40,318][INFO ][o.e.n.Node               ] [NggTRJz] node name [NggTRJz] derived from node ID; set [node.name] to override
elasticsearch_1  | [2016-11-23T00:25:40,323][INFO ][o.e.n.Node               ] [NggTRJz] version[5.0.0], pid[1], build[253032b/2016-10-26T05:11:34.737Z], OS[Linux/3.13.0-46-generic/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_111/25.111-b14]
elasticsearch_1  | [2016-11-23T00:25:46,035][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2016-11-23T00:25:46,035][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [ingest-common]
elasticsearch_1  | [2016-11-23T00:25:46,035][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [lang-expression]
elasticsearch_1  | [2016-11-23T00:25:46,035][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [lang-groovy]
elasticsearch_1  | [2016-11-23T00:25:46,036][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [lang-mustache]
elasticsearch_1  | [2016-11-23T00:25:46,036][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [lang-painless]
elasticsearch_1  | [2016-11-23T00:25:46,036][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [percolator]
elasticsearch_1  | [2016-11-23T00:25:46,036][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [reindex]
elasticsearch_1  | [2016-11-23T00:25:46,036][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [transport-netty3]
elasticsearch_1  | [2016-11-23T00:25:46,037][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded module [transport-netty4]
elasticsearch_1  | [2016-11-23T00:25:46,047][INFO ][o.e.p.PluginsService     ] [NggTRJz] loaded plugin [x-pack]
elasticsearch_1  | [2016-11-23T00:25:47,319][WARN ][o.e.d.s.g.GroovyScriptEngineService] [groovy] scripts are deprecated, use [painless] scripts instead
elasticsearch_1  | [2016-11-23T00:25:56,612][INFO ][o.e.n.Node               ] [NggTRJz] initialized
elasticsearch_1  | [2016-11-23T00:25:56,612][INFO ][o.e.n.Node               ] [NggTRJz] starting ...
elasticsearch_1  | [2016-11-23T00:25:57,508][INFO ][o.e.t.TransportService   ] [NggTRJz] publish_address {172.18.0.4:9300}, bound_addresses {[::]:9300}
elasticsearch_1  | [2016-11-23T00:25:57,520][INFO ][o.e.b.BootstrapCheck     ] [NggTRJz] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
elasticsearch_1  | [2016-11-23T00:26:01,065][INFO ][o.e.c.s.ClusterService   ] [NggTRJz] new_master {NggTRJz}{NggTRJzwT4eGoUsotkGM0A}{K5vYMzO7SUG-0HZVOqQTWw}{172.18.0.4}{172.18.0.4:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
elasticsearch_1  | [2016-11-23T00:26:01,226][INFO ][o.e.h.HttpServer         ] [NggTRJz] publish_address {172.18.0.4:9200}, bound_addresses {[::]:9200}
elasticsearch_1  | [2016-11-23T00:26:01,226][INFO ][o.e.n.Node               ] [NggTRJz] started
kibana_1         | Starting Kibana
elasticsearch_1  | [2016-11-23T00:26:01,633][INFO ][o.e.g.GatewayService     ] [NggTRJz] recovered [0] indices into cluster_state
elasticsearch_1  | [2016-11-23T00:26:04,968][INFO ][o.e.m.j.JvmGcMonitorService] [NggTRJz] [gc][8] overhead, spent [255ms] collecting in the last [1s]
elasticsearch_1  | [2016-11-23T00:26:07,084][INFO ][o.e.x.m.e.Exporters      ] [NggTRJz] skipping exporter [default_local] as it isn't ready yet
elasticsearch_1  | [2016-11-23T00:26:07,084][ERROR][o.e.x.m.AgentService     ] [NggTRJz] exception when exporting documents
elasticsearch_1  | org.elasticsearch.xpack.monitoring.exporter.ExportException: exporters are either not ready or faulty
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:188) ~[x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.AgentService$ExportingWorker.run(AgentService.java:208) [x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:13Z","tags":["status","plugin:kibana@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:13Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:14Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:14Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:14Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:14Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:14Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
logstash_1       | Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties.
elasticsearch_1  | [2016-11-23T00:26:17,549][INFO ][o.e.c.m.MetaDataCreateIndexService] [NggTRJz] [.monitoring-es-2-2016.11.23] creating index, cause [auto(bulk api)], templates [.monitoring-es-2], shards [1]/[1], mappings [shards, _default_, node, index_stats, index_recovery, cluster_state, cluster_stats, indices_stats, node_stats]
elasticsearch_1  | [2016-11-23T00:26:18,073][INFO ][o.e.c.m.MetaDataCreateIndexService] [NggTRJz] [.monitoring-data-2] creating index, cause [auto(bulk api)], templates [.monitoring-data-2], shards [1]/[1], mappings [node, cluster_info, kibana]
elasticsearch_1  | [2016-11-23T00:26:19,016][INFO ][o.e.c.m.MetaDataMappingService] [NggTRJz] [.monitoring-es-2-2016.11.23/-AEPo8pmRoW0eDALvM_45g] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-23T00:26:19,506][INFO ][o.e.c.m.MetaDataMappingService] [NggTRJz] [.monitoring-es-2-2016.11.23/-AEPo8pmRoW0eDALvM_45g] update_mapping [node_stats]
dockerelk_logstash_1 exited with code 1
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:20Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:20Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:20Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:20Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
elasticsearch_1  | [2016-11-23T00:26:20,480][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [buildNum]
elasticsearch_1  | [2016-11-23T00:26:20,481][INFO ][o.e.c.m.MetaDataCreateIndexService] [NggTRJz] [.kibana] creating index, cause [api], templates [], shards [1]/[1], mappings [server, config]
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:20Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:21Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch: mode: trial | status: active | expiry date: 2016-12-23T00:26:08+00:00"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:21Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from green to yellow - Waiting for Monitoring Health Check","prevState":"green","prevMsg":"Ready"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:21Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:21Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:21Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:24Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Monitoring Health Check"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["status","plugin:security@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["security","warning"],"pid":1,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["status","plugin:console@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["status","plugin:timelion@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0.0.0.0:5601"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:26:28Z","tags":["status","ui settings","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1  | [2016-11-23T00:26:29,811][INFO ][o.e.c.m.MetaDataMappingService] [NggTRJz] [.monitoring-es-2-2016.11.23/-AEPo8pmRoW0eDALvM_45g] update_mapping [index_stats]
elasticsearch_1  | [2016-11-23T00:26:29,918][INFO ][o.e.c.m.MetaDataMappingService] [NggTRJz] [.monitoring-es-2-2016.11.23/-AEPo8pmRoW0eDALvM_45g] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-23T00:26:29,981][INFO ][o.e.c.m.MetaDataMappingService] [NggTRJz] [.monitoring-es-2-2016.11.23/-AEPo8pmRoW0eDALvM_45g] update_mapping [indices_stats]
elasticsearch_1  | [2016-11-23T00:26:31,265][INFO ][o.e.c.m.MetaDataCreateIndexService] [NggTRJz] [.monitoring-kibana-2-2016.11.23] creating index, cause [auto(bulk api)], templates [.monitoring-kibana-2], shards [1]/[1], mappings [_default_, kibana_stats]

After the max_vm_count step, please restart the stack using docker-compose down && docker-compose up.

Yes , I tried those steps and I got the above error.

Try to start logstash with a debug log level:
Update the logstash definition in the file docker-compose.yml with:
  logstash:
    build: logstash/
    command: -f /etc/logstash/conf.d/ --log.level debug
    volumes:
      - ./logstash/config:/etc/logstash/conf.d
    ports:
      - "5000:5000"
    networks:
      - docker_elk
    depends_on:
      - elasticsearch

And  restart the stack using docker-compose down && docker-compose up.
Note, I'm not sure if it's related but it seems there is an issue when elasticsearch is trying to boot:
elasticsearch_1  | org.elasticsearch.xpack.monitoring.exporter.ExportException: exporters are either not ready or faulty
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:188) ~[x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.AgentService$ExportingWorker.run(AgentService.java:208) [x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]

Got the same error:
Creating network "dockerelk_docker_elk" with driver "bridge"
Creating dockerelk_elasticsearch_1
Creating dockerelk_logstash_1
Creating dockerelk_kibana_1
Attaching to dockerelk_elasticsearch_1, dockerelk_kibana_1, dockerelk_logstash_1
kibana_1         | Stalling for Elasticsearch
elasticsearch_1  | [2016-11-23T00:50:22,785][INFO ][o.e.n.Node               ] [] initializing ...
elasticsearch_1  | [2016-11-23T00:50:23,051][INFO ][o.e.e.NodeEnvironment    ] [-ZgcK4i] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/disk/by-uuid/21813bed-571e-4fcc-905d-32bc13641493)]], net usable_space [12.6gb], net total_space [29.4gb], spins? [possibly], types [ext4]
elasticsearch_1  | [2016-11-23T00:50:23,054][INFO ][o.e.e.NodeEnvironment    ] [-ZgcK4i] heap size [1007.3mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2016-11-23T00:50:23,061][INFO ][o.e.n.Node               ] [-ZgcK4i] node name [-ZgcK4i] derived from node ID; set [node.name] to override
elasticsearch_1  | [2016-11-23T00:50:23,065][INFO ][o.e.n.Node               ] [-ZgcK4i] version[5.0.0], pid[1], build[253032b/2016-10-26T05:11:34.737Z], OS[Linux/3.13.0-46-generic/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_111/25.111-b14]
elasticsearch_1  | [2016-11-23T00:50:29,081][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2016-11-23T00:50:29,084][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [ingest-common]
elasticsearch_1  | [2016-11-23T00:50:29,089][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [lang-expression]
elasticsearch_1  | [2016-11-23T00:50:29,090][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [lang-groovy]
elasticsearch_1  | [2016-11-23T00:50:29,094][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [lang-mustache]
elasticsearch_1  | [2016-11-23T00:50:29,094][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [lang-painless]
elasticsearch_1  | [2016-11-23T00:50:29,096][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [percolator]
elasticsearch_1  | [2016-11-23T00:50:29,098][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [reindex]
elasticsearch_1  | [2016-11-23T00:50:29,098][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [transport-netty3]
elasticsearch_1  | [2016-11-23T00:50:29,099][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded module [transport-netty4]
elasticsearch_1  | [2016-11-23T00:50:29,110][INFO ][o.e.p.PluginsService     ] [-ZgcK4i] loaded plugin [x-pack]
elasticsearch_1  | [2016-11-23T00:50:30,683][WARN ][o.e.d.s.g.GroovyScriptEngineService] [groovy] scripts are deprecated, use [painless] scripts instead
elasticsearch_1  | [2016-11-23T00:50:39,188][INFO ][o.e.n.Node               ] [-ZgcK4i] initialized
elasticsearch_1  | [2016-11-23T00:50:39,191][INFO ][o.e.n.Node               ] [-ZgcK4i] starting ...
elasticsearch_1  | [2016-11-23T00:50:39,969][INFO ][o.e.t.TransportService   ] [-ZgcK4i] publish_address {172.18.0.2:9300}, bound_addresses {[::]:9300}
elasticsearch_1  | [2016-11-23T00:50:39,998][INFO ][o.e.b.BootstrapCheck     ] [-ZgcK4i] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
elasticsearch_1  | [2016-11-23T00:50:43,716][INFO ][o.e.c.s.ClusterService   ] [-ZgcK4i] new_master {-ZgcK4i}{-ZgcK4iPSumdPzQ7bhqmiw}{hqR8sCA0SsuhCmYo-SEjnw}{172.18.0.2}{172.18.0.2:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
elasticsearch_1  | [2016-11-23T00:50:43,908][INFO ][o.e.h.HttpServer         ] [-ZgcK4i] publish_address {172.18.0.2:9200}, bound_addresses {[::]:9200}
elasticsearch_1  | [2016-11-23T00:50:43,936][INFO ][o.e.n.Node               ] [-ZgcK4i] started
kibana_1         | Starting Kibana
elasticsearch_1  | [2016-11-23T00:50:44,481][INFO ][o.e.g.GatewayService     ] [-ZgcK4i] recovered [0] indices into cluster_state
elasticsearch_1  | [2016-11-23T00:50:47,527][INFO ][o.e.m.j.JvmGcMonitorService] [-ZgcK4i] [gc][8] overhead, spent [265ms] collecting in the last [1s]
elasticsearch_1  | [2016-11-23T00:50:49,683][INFO ][o.e.x.m.e.Exporters      ] [-ZgcK4i] skipping exporter [default_local] as it isn't ready yet
elasticsearch_1  | [2016-11-23T00:50:49,684][ERROR][o.e.x.m.AgentService     ] [-ZgcK4i] exception when exporting documents
elasticsearch_1  | org.elasticsearch.xpack.monitoring.exporter.ExportException: exporters are either not ready or faulty
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:188) ~[x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at org.elasticsearch.xpack.monitoring.AgentService$ExportingWorker.run(AgentService.java:208) [x-pack-5.0.0.jar:5.0.0]
elasticsearch_1  | 	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:kibana@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:50:55Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1  | [2016-11-23T00:50:59,970][INFO ][o.e.c.m.MetaDataCreateIndexService] [-ZgcK4i] [.monitoring-es-2-2016.11.23] creating index, cause [auto(bulk api)], templates [.monitoring-es-2], shards [1]/[1], mappings [_default_, node, shards, index_stats, index_recovery, cluster_state, cluster_stats, indices_stats, node_stats]
elasticsearch_1  | [2016-11-23T00:51:00,257][INFO ][o.e.c.m.MetaDataCreateIndexService] [-ZgcK4i] [.monitoring-data-2] creating index, cause [auto(bulk api)], templates [.monitoring-data-2], shards [1]/[1], mappings [node, cluster_info, kibana]
elasticsearch_1  | [2016-11-23T00:51:00,602][INFO ][o.e.c.m.MetaDataMappingService] [-ZgcK4i] [.monitoring-es-2-2016.11.23/nafAKXpPRwGrxcZt-o274w] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-23T00:51:00,778][INFO ][o.e.c.m.MetaDataMappingService] [-ZgcK4i] [.monitoring-es-2-2016.11.23/nafAKXpPRwGrxcZt-o274w] update_mapping [node_stats]
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:02Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:02Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:02Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:02Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - No existing Kibana index found","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
elasticsearch_1  | [2016-11-23T00:51:02,067][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [buildNum]
elasticsearch_1  | [2016-11-23T00:51:02,070][INFO ][o.e.c.m.MetaDataCreateIndexService] [-ZgcK4i] [.kibana] creating index, cause [api], templates [], shards [1]/[1], mappings [server, config]
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:02Z","tags":["status","plugin:elasticsearch@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:03Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch: mode: trial | status: active | expiry date: 2016-12-23T00:50:50+00:00"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:03Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"yellow","message":"Status changed from green to yellow - Waiting for Monitoring Health Check","prevState":"green","prevMsg":"Ready"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:03Z","tags":["status","plugin:xpack_main@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:03Z","tags":["status","plugin:graph@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:03Z","tags":["status","plugin:reporting@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"No existing Kibana index found"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:05Z","tags":["status","plugin:monitoring@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Monitoring Health Check"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:08Z","tags":["status","plugin:security@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:08Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:08Z","tags":["security","warning"],"pid":1,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:08Z","tags":["status","plugin:console@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:09Z","tags":["status","plugin:timelion@5.0.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:09Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0.0.0.0:5601"}
kibana_1         | {"type":"log","@timestamp":"2016-11-23T00:51:09Z","tags":["status","ui settings","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
elasticsearch_1  | [2016-11-23T00:51:11,015][INFO ][o.e.c.m.MetaDataMappingService] [-ZgcK4i] [.monitoring-es-2-2016.11.23/nafAKXpPRwGrxcZt-o274w] update_mapping [index_stats]
elasticsearch_1  | [2016-11-23T00:51:11,081][INFO ][o.e.c.m.MetaDataMappingService] [-ZgcK4i] [.monitoring-es-2-2016.11.23/nafAKXpPRwGrxcZt-o274w] update_mapping [cluster_stats]
elasticsearch_1  | [2016-11-23T00:51:11,157][INFO ][o.e.c.m.MetaDataMappingService] [-ZgcK4i] [.monitoring-es-2-2016.11.23/nafAKXpPRwGrxcZt-o274w] update_mapping [indices_stats]
elasticsearch_1  | [2016-11-23T00:51:13,113][INFO ][o.e.c.m.MetaDataCreateIndexService] [-ZgcK4i] [.monitoring-kibana-2-2016.11.23] creating index, cause [auto(bulk api)], templates [.monitoring-kibana-2], shards [1]/[1], mappings [_default_, kibana_stats]
logstash_1       | Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties.
dockerelk_logstash_1 exited with code 1

From the error stack you posted earlier, I'm guessing its looking for Java 1.8, my java_home is set to 1.7. Does Java_version have anything to do with this.
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]

No it's the java version shipped in the containers. No idea here... you'll have to find a way to access logstash logs to find out the issue.

Ok thanks for looking into this , I'll keep digging further.

@rohan04: Logstash 5.2 seems to require the log4j2.properties file in its config directory (see README).
If you mount the entire logstash/config/ you have to make sure you include this file.
Can you try that on the current master and close this issue if it solves your problem?

kibana_1         | {"type":"error","@timestamp":"2020-05-19T11:07:00Z","tags":["fatal"],"pid":1,"level":"fatal","error":{"message":"child "elasticsearch" fails because ["hosts" is not allowed]","name":"ValidationError","stack":"ValidationError: child "elasticsearch" fails because ["hosts" is not allowed]\n    at Object.exports.process (/usr/share/kibana/node_modules/joi/lib/errors.js:181:19)\n    at _validateWithOptions (/usr/share/kibana/node_modules/joi/lib/any.js:651:31)\n    at root.validate (/usr/share/kibana/node_modules/joi/lib/index.js:121:23)\n    at Config._commit (/usr/share/kibana/src/server/config/config.js:119:35)\n    at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n    at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n    at /usr/share/kibana/src/plugin_discovery/plugin_config/extend_config_service.js:22:12\n    at next (native)\n    at step (/usr/share/kibana/src/plugin_discovery/plugin_config/extend_config_service.js:45:191)\n    at /usr/share/kibana/src/plugin_discovery/plugin_config/extend_config_service.js:45:361"},"message":"child "elasticsearch" fails because ["hosts" is not allowed]"}
dockerelk_elasticsearch_1 exited with code 1
dockerelk_kibana_1 exited with code 1

@charan-code this issue is closed, please open a new issue.

Thanks alotttt sir, will try and tell u

authors: antoineco charan-code deviantony rohan04


text:
Convert bi-annual to semi-annual

Small grammar suggestion

Is there a reason you dislike the term "bi-annual"?
https://www.merriam-webster.com/dictionary/biannual

@chrisl8 TIL! The "did you know" block (pasted below just so you know where I'm coming from) and second definition from your link describe how I've always understood biannual, but the primary definition is clearly 2x / year! And it looks like MW is actually generous to the "biannual can == biennial" crowd relative to other sources. So I'll just close this out!

Did You Know?
When we describe something as biannual, we can mean either that it occurs twice a year or that it occurs once every two years. So how does someone know which particular meaning we have in mind? Well, unless we provide them with a contextual clue, they don't. Some people prefer to use semiannual to refer to something that occurs twice a year, reserving biannual for things that occur once every two years. This practice is hardly universal among English speakers, however, and biannual remains a potentially ambiguous word. Fortunately, English also provides us with biennial, a word that specifically refers to something that occurs every two years or that lasts or continues for two years.

source: gharchive/pull-request

repo: devict/ictgamejam-guide

license: MIT

license_type: permissive

license_source: github-api


text:
Support hapi v15

25 tests complete
Test duration: 576 ms
Assertions count: 115 (verbosity: 4.60)
No global variable leaks detected
Coverage: 100.00%
Linting results: No issues

Thanks!  Will get this out asap.

authors: devinivy pwarnock

repo: devinivy/dogwater

license: mit

license_source: bigquery


text:
nested derivatives of staggered fields seem broken

p = TimeFunction(name="p", grid=grid, space_order=4, staggered=x)

then this one is good:
In [13]: p.dx.evaluate
Out[13]: 0.0833333333*p(t, x - 3*h_x/2, y, z)/h_x - 0.666666667*p(t, x - h_x/2, y, z)/h_x + 0.666666667*p(t, x + 3*h_x/2, y, z)/h_x - 0.0833333333*p(t, x + 5*h_x/2, y, z)/h_x

but this one is not:
In [14]: p.dx.dx.evaluate
Out[14]: 4.36557457e-11*(0.0833333333*p(t, x - 3*h_x/2, y, z)/h_x - 0.666666667*p(t, x - h_x/2, y, z)/h_x + 0.666666667*p(t, x + 3*h_x/2, y, z)/h_x - 0.0833333333*p(t, x + 5*h_x/2, y, z)/h_x)/h_x

clearly missing terms
potential patch as suggested by @mloubout :
line 283 of finite_differences/finite_difference.py, replace
terms.append(expr._subs(expr.indices_ref[dim], iloc) * c)

with
terms.append(expr._subs(dim, iloc - (expr.indices_ref[dim] - dim)) * c)

then to be tested and equipped with tests which are apparently missing

fixed via #1465

source: gharchive/issue

repo: devitocodes/devito


text:
compiler: Revamp lowering of IndexDerivatives

Superseds #2183
No new features added; mostly restructuring, improvements, tweaks, minor fixes

I was nearly forgetting.
Bonus:
compilation speed now approx twice as fast


text:
Fix respond_to? signature

While developing a Rails 4.2 application, I got warnings like this:
/usr/home/nilsding/Projects/myapp/app/views/header/_login.haml:7: warning: #<Class:0x000008115ccdd0>#respond_to?(:respond_to_missing?) is old fashion which takes only one parameter
/usr/home/nilsding/.rvm/gems/ruby-2.3.1@myapp/gems/mountain_view-0.9.0/app/helpers/mountain_view/application_helper.rb:15: warning: respond_to? is defined here

This commit silences the warning by adding another optional parameter to the method's signature.

Thanks!!

authors: kitop nilsding


text:
🛑 Photoz ICVJ is down

In ef3032e, Photoz ICVJ (https://photoz-icvj.onrender.com/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Photoz ICVJ is back up in fc8b8b2 after 10 minutes.

repo: devnullsans/upptime-monitor


text:
Create CODEOWNERS

Purpose

...
Testing the code

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Please modify line 1

Changes are made.

,,,,


text:
Visualizing Workflow - typo

In Building Kanban Board
teams -> team's

Fixed in #28


text:
[BUG] Hover effect is not proper on Join Us in Navbar section.

Is there any existing issue for this?

[X] I have searched the existing issues

Description
Hover effect on Join Us is not proper in navbar section.
Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
No response

Duplicate issue. Check #343

repo: devs-in-tech/DevsInTech


text:
Can't build dependency with image tag including DEVSPACE_GIT_COMMIT

What happened?
I have included a dependency:
- source:
    git: https://github.com/FactFiber/devspace-nginx-auth-jwt

Which configures tags as:
    tag: ${DEVSPACE_GIT_COMMIT}-${DEVELOPER}-${DEVSPACE_RANDOM}

When I try to deploy, I get the message:
[fatal]  Error deploying dependencies: resolve dependencies: resolve dependencies recursive: loading config for dependency https://github.com/FactFiber/devspace-nginx-auth-jwt - profile dev: No git repository found, but predefined var DEVSPACE_GIT_COMMIT is used

What did you expect to happen instead?
I expect that, since devspace is loading the dependency from a git repo, it should be able to figure out the commit.
How can we reproduce the bug? (as minimally and precisely as possible)
I believe that the above should allow you to recreate.
Local Environment:

Operating System: mac
Deployment method: helm

Kubernetes Cluster:

Cloud Provider: na
Kubernetes Version: na

Anything else we need to know?

/kind bug

@shaunc thanks for opening this issue! This should be fixed with #948

authors: FabianKramm shaunc

repo: devspace-cloud/devspace


text:
summernote image field has bug which a image file doesn't delete when a field is removed.

This is an original Summernote bug. Looking at the code, it looks asynchronous to the "django user table".
After parsing the text file, it can be run as if using the image URL.
Fixing bugs requires a lot of consideration when managing files and folders.
So I will choose between making my own or using an open source library.
After testing some open source, if I can't find a solution, I handle summernote's config file with my own code.

django-cleanup is not working in summernote.
Summernote seems like doesn't have any delete process with using urls module.
So, It doesn't work.
I have a idea that use new class with hooked summernote urls.
But It require modifing forked new django-summernote repository or use js with custom own view class.
this is not main job on my project.
so the status is being pending.
later, I'll handle it using js first.
and will try pull request to django-summernote with own idea.

repo: devspoon/devspoon-portfolio-blog


text:
Merge release-0.5 branch to main branch

Summary
Merge release-0.5 branch to main branch

/cc @aeinrw

repo: devstream-io/devstream


text:
⚠ Mobitopup has degraded performance

In b049dba, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 11797 ms

Resolved: Mobitopup performance has improved in 5239752.


text:
Any possible update on 4.2?

Still waiting for it..

watch @Jaehyuk-Lee 's Fork: link

Actually, my fork version (also this original DFAssist) doesn't supports v4.2 well. You should see the "Logs" tab in main window to check matched duty. Matching duty code was changed after 4.2 patch.

보낸 사람: LalafellSleep notifications@github.com
보낸 날짜: 2018년 5월 18일 금요일 오전 7:14
받는 사람: devunt/DFAssist
참조: Jaehyuk-Lee; Mention
제목: Re: [devunt/DFAssist] Any possible update on 4.2? (#106)
watch @Jaehyuk-Leehttps://github.com/Jaehyuk-Lee 's Fork: linkhttps://github.com/Jaehyuk-Lee/DFAssist/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/devunt/DFAssist/issues/106#issuecomment-390030947, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEelSyfxf_iJ7VD7kSip2mQn-D5aXFuVks5tzfY4gaJpZM4UCL1b.

authors: Jaehyuk-Lee junyahuang lalafellsleep

repo: devunt/DFAssist

license: unlicense


text:
[feature/removeVariable] replace Variable on BehaviourRelay

Hi, thank you for your great work!
This PR allows migrate ReactorKit on Behavior & Publish Relays instead of own types.

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #16   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines          78     78
=====================================
  Hits           78     78

Impacted Files
Coverage Δ

Sources/RxExpect/RxExpect.swift
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c3a3bb3...9432f9c. Read the comment docs.

authors: MortyMerr codecov-io

repo: devxoul/RxExpect


text:
Add TVOS & OSX target in project and cocoapod podspec

For carthage

I edit "product name" of the two xcode project targets to "Then"
I share the scheme

@phimage, thanks for your work! Especially for podspec.
However, why do we need seperated targets?

For cocoapod no need to add targets
For xcode we need to test the compilation using the corresponding OS (even if there is no UIKit, Cocoa dependencies)
One target = one OS
And carthage use the shared scheme of target to compile for each OS (in separated folder)

Scheme is already shared. For travis, I think this PR should have test code for each targets.
But actually I'm not sure separating target is necessary.

Test code for each target is not mandatory except complex codes or issue with 32/64 bits, many projects choose one OS to do unit tests
Ok you look for the more clean way to add other OS. Until know I see only project with multiples targets. If its the directories that bother you (ThenOSX, ThenTVOS) it's possible to remove them or regroup them (the requirements is that files must exist and added to targets, no matter where the files are)

Oh, I mean the .travis.yml file. Apologize for unclear words. (For example, https://github.com/devxoul/SwiftyColor/blob/master/.travis.yml)
Exactly. I don't want to make directories for each targets. Well, how about SwiftyJSON's approach? I think it seemed to be more clean :smile:

I do it

share the header .h between the targets
Move plist file into the unique folder Support and add in xcode a "group"
그럼 remove useless files and folders

@phimage, thank you very much :smile::+1:

authors: devxoul phimage

repo: devxoul/Then


text:
The official openai package no longer uses axios

The README on this project says this:

Unfortunately, the official openai-node uses Axios, which only supports Node and is bloated.

Reasons to consider using openai-fetch:
Supports all envs with native fetch: Node 18+, browsers, Deno, Cloudflare Workers, etc

As of https://github.com/openai/openai-node/releases/tag/v4.0.0, openai uses the native fetch by default in Deno, Cloudflare workers, etc. It does use node-fetch in Node 18+, though may be moving to undici there soon.
The package download size stats may have changed as well, though most of the size of the official package is types, sourcemaps, etc which aren't imported at runtime. The runtime impact is usually around 25kb (still larger than this package).

If there's anything still missing from the openai package that you'd like to see, please do let me know!

This is updated on the v2 branch which will be merged soon.

authors: rattrayalex rileytomasek

repo: dexaai/openai-fetch


text:
Generated (x,y) positions are off

@dfcreative
From
const regl = require('regl')({ extensions: 'oes_element_index_uint' })
const createMatrix = require('./')

// create splom instance
let splom = createMatrix(regl)

splom.update({
  data: [
    [1, 2, 3],
    [4, 6, 8]
  ],
  ranges: [
    [0, 10],
    [0, 10]
  ]
})

splom.draw()

I get:

where the the top-left panel which is supposed to plot x=[1,2,3] vs y=[4,6,8] is plotting instead x=[4,6,8] vs y=[1,2,3] and similarly for the bottom-right panel.

Whoops, sorry. Fixed 6a6cd43b514769e7ecc9a400cd75f8e2325184ea

Wow that was fast. Thanks!!!

authors: dfcreative etpinard

repo: dfcreative/regl-scattermatrix


text:
Change all instances of "git" to "Git"

Describe the bug
The Gov.UK technical style guide recommends that Git should always start with a capital letter. There are quite a few instances where it's written as "git" throughout the Analysts Guide.
To Reproduce
In RStudio you can CTRL+Shift+F to search all scripts for "git". Make sure you tick the case sensitivity box.
There's no need to correct "git" to "Git" in any URLs so watch out for those when you search.

I can do this one!

#103
#104
#105
#106

authors: inane-pixel jen-machin

repo: dfe-analytical-services/analysts-guide


text:
Page 1: You have to double click on tables for cross filtering

Currently if you click on one of the tables it filters the others, if you then click on one of the other tables it wipes the other selections, but doesn't register your selection, you have to select again.
It would be nice to handle this a bit better for users so that a single click would make the selection.

Have a fix in progress for this on a branch adding a dropdown to the first page


text:
bug: Ed25519KeyIdentity fails signature check against mainnet

Describe the bug
When trying to initialize a HTTPAgent from a secretKey, the request fails with the following error:
Error: Server returned an error:
  Code: 403 (Forbidden)
  Body: Failed to authenticate request
[redacted] due to: Verifying signature for [redacted] failed: Ed25519 signature could not be verified: public key [redacted], signature [redacted], error: signature error

To Reproduce
Steps to reproduce the behavior:
clone and set up https://github.com/FleekHQ/ic-auth-test
Follow directions in readme
npm i @types/node
add dist to tsconfig exclude
run build
node dist/index
Expected behavior
A clear and concise description of what you expected to happen.
The agent should be able to make authenticated calls via the wallet using an identity generated from the same secret key that controls the wallet

@hansl determined that the solution will be to generate and save the key not using dfx but using JavaScript using our own Ed25519KeyIdentity classes.
Action item to resolve this ticket will be to deprecate the fromSecretKey method and to add documentation on how to use the fromJSON and toJSON methods for this use case

repo: dfinity/agent-js


text:
BNT-2: Invoice Canister

Overview

Status: Assigned
Project Type: Traditional - One worker contributes, and one worker is paid
Time Commitment: Weeks
Experience Level: Intermediate
Size: USD 5000 in ICP (at time of distribution)

Description
The invoice canister provides a simple interface for creating and paying invoices in various tokens on the Internet Computer. It is a custodial solution, intended to be a simple, drop-in payment solution for any canister.
The invoice canister project has been started by DFINITY but needs additional work to make it production-ready. The main points to be tackled in this bounty are:

Support for the ICRC-1 fungible token standard
The following, mainly security-related, issues need to be resolved:

https://github.com/dfinity/invoice-canister/issues
https://github.com/dfinity/examples/issues/292

Acceptance Criteria

All open issues have been addressed
A test case using the ICRC-1 standard can be demonstrated
A PR with all changes has been merged into  https://github.com/dfinity/examples/

How to apply?
Add a comment to this issue or contact us on the #grants channel in the Developer Discord. Please provide some background on your experience and give an outline of your project plan.
References
Forum post: https://forum.dfinity.org/t/payments-invoice-canister-design-review/
Code: https://github.com/dfinity/examples/tree/master/motoko/invoice-canister

Hello, I'd like to apply for this bounty.
I recently completed a grant of my own (https://github.com/AshtonEngberg/doyoutodo), and one of the use cases that emerged in the course of that work was creating a "billable hours" dapp that could be integrated the direct ECDSA signing. To get from what I developed to that, I'd need to implement an invoices services which dovetails neatly into this bounty. I've also been attending the Token & Ledger working group and am familiar with the ICRC-1 standard.
To start I'd implement a minimalistic front-end for the existing invoice canister code, which is not strictly necessary but important for demonstrating the functionality, and it would give me an opportunity to get to know the code well enough. With that implemented, I'd finish off the simpler unrelated open issues such as using dependencies instead of hard-code libraries, progressing into user access control to handle the others, and then do integration with a novel token implementing the ICRC-1 standard. Each iteration of the development would come with test cases, and I'd finish the work adding the needed documentation as well as a developer experience article walking through using the integration of an ICRC-1 token.
I'd commit to working full time on this, and estimate it would take me between 6-8 weeks to complete. Let me know if there is any other information I can provide. This bounty is just the project I've been looking forward to do, and I would get started immediately.

Hey @AshtonEngberg, thank you for your interest! I'll have a look at your previous work and will get in contact with you shortly.
FYI, I've seen that @krpeacock did some more work: https://github.com/dfinity/examples/pull/356

Thanks for getting back to me. I should also point out I attended the
Motoko Bootcamp, built the backend canister for the BlueBird project shown
at Supernova, and have previous professional programming experience
developing Android applications including building an Android SDK for an
in-memory trie based search engine called SRCH2 as well as the Android
Surfline app, though I don't know if the code I created is the same (though
the frontend is still). This bounty would be a great opportunity to apply
my Motoko skills in a well defined and important use case. Thanks again for
the consideration.
On Tue, Nov 1, 2022 at 5:07 AM Dominic Wörner @.***>
wrote:

Hey @AshtonEngberg https://github.com/AshtonEngberg, thank you for your
interest! I'll have a look at your previous work and will get in contact
with you shortly.
FYI, I've seen that @krpeacock https://github.com/krpeacock did some
more work: dfinity/examples#356
https://github.com/dfinity/examples/pull/356
—
Reply to this email directly, view it on GitHub
https://github.com/dfinity/grant-rfps/issues/2#issuecomment-1298241223,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZT4UZ4HISF7QJAO6Z6OEDWGDMTXANCNFSM57KKOWUA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @AshtonEngberg, please contact me on Discord (domwoe#9301). It would be great to have a quick chat.

Just a quick note, I finished changes necessary for the last pull request to be completed which can be viewed here:
https://github.com/AshtonEngberg/examples/tree/ashton/invoice-finish-cleanup-merge
I didn't know the procedure for contributing to Kyle's pull request, so I forked the examples repo, pulled the PR branch, made changes, and pushed them back to the fork repo to show what had been done. Integrating the nns-ledger (dfx nns install) also became a part of this pull request, which does work although may not be ideal yet (mostly, resseting the nns-ledger in particular also reinstalls all 8 nns ledgers, which afaik there's not another way to do this when using dfx nns install yet). If not, I can also push another branch using the manual download and deploying of an ICP ledger to finish the PR if that's the path forward, just let me know.

Should the ICRC1 subaccount encoding match that of the ICP subaccount for invoices/invoice creators?
The difference is a padding of the four bytes for the CRC32 encoding check, I can just make them the same but this seems like it could give the incorrect impression they have to match.

Completed with https://github.com/dfinity/examples/pull/465

authors: AshtonEngberg atengberg domwoe

repo: dfinity/grant-rfps


text:
chore: 📝 updated II integration docs

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[x] You have updated the .github/CODEOWNERS file according to your changes.
[x] You have registered new documents to /sidebars.js if any.

This PR appears to be outdated/not needed. Closing this PR to clean up the repo. Please feel free to reopen if you think this should be revisited.

repo: dfinity/portal


text:
ICRC-3x: extract icrc-3x_batch_calls

This PR intends to extract the following standard extensions:

ICRC-3x: Batch Calling

This is a collaborative change by @frederikrothenberger and @plitzenberger

@plitzenberger : This PR now needs updating with a different number (because of #116 ).

@plitzenberger : This PR now needs updating with a different number (because of #116 ).

I assigned it ICRC-39.

@plitzenberger: I changed the processing of additional requests after a failure to avoid footguns resulting from partially successful batches.

authors: frederikrothenberger plitzenberger

repo: dfinity/wg-identity-authentication


text:
Source grouper-provided data to original sources, not VICC normalizer

(Be a little bit more purposeful about what is extracted, also)

Closed in #109


text:
Improve article 2110.05444

Exact location of issue
First paragraph after the last image of: https://ar5iv.org/html/2110.05444
Problem details
All listing references are shown as "(LABEL:code:socket)".
(Optional) Expected behavior
Expecting "Listing 2.".

Listing labels seem to need a patch:
\begin{lstlisting}[caption=Socket class object state refinement, label=code:socket, basicstyle=\small]

authors: alcides dginev


text:
t is not a constructor (using .min.js from jsdelivr 1.1.0)

I'm attempting to use this on my webpage (it's an internal company one) but the Chrome devtools keep coming up about 't is not a constructor'.
All i'm doing is:
window['delegate-events'].on('click', '.btn-delete', function(e) { console.log(e); });

.btn-delete is a button on a dynamic table row, the error occurs when I load the page, if I then click on the button it does nothing.

It would appear, that to use this in the browser, one also needs to make sure they have the 'Selector-set' JS loaded before hand.
Once I did that, the library started working just fine.

repo: dgraham/delegated-events


text:
Use npx to get at the correct eslint executable.

I propose to use the npx runner to get at the correct eslint executable.
See:
https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b

Using npx will result in a network call if eslint is not installed. So we would need to run it as npm --no-install to prevent that and ensure only a locally installed binary is used.
Can you explain more about why you prefer calling npx rather than invoking the eslint binary directly? Is the auto-install feature important?

Hi David,
The auto-install feature is totally unimportant for me. I added --no-install.
The relevant behaviour for me is to have it work when I am standing in a subdirectory. Currently it only works if you are in the directory containing (the correct) ./node_modules directly.

Thanks!

repo: dgraham/vim-eslint


text:
Incrporate feedback from manish

Tests have to be fixed so commented some of them out for now.

This change is

Review status: 0 of 9 files reviewed at latest revision, 1 unresolved discussion.

server/interact/interact.proto, line 7 [r2] (raw file):

service GruQuiz {
	rpc Authenticate (Token) returns (Session) {}

Wonder where is this weird character coming from, tab is set to 8 spaces in my editor.

Comments from Reviewable

Reviewed 3 of 7 files at r1, 6 of 6 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

server/main.go, line 579 [r2] (raw file):

		for _, tag := range q.Tags {
			if tag[0] < 'a' || tag[0] > 'z' {

tags could contain dashes. Allow for that.

Comments from Reviewable

Merged

authors: manishrjain pawanrawal

repo: dgraph-io/gru


text:
Added navbar to index.html with required CSS and JS

Related Issue
Issue No.: [#242 ]
Email ID used to register for VSoc'24
Email ID: [atharavashihurkar@gmail.com]
Description
I have designed a navbar as per your requirements. It features a sleek and classy look, providing an extraordinary visual experience. The text '50 Days, 50 Web Projects' has been replaced with a logo image, which is customized with hover and other effects using CSS to enhance its interactivity. Please find the attached video showcasing the design and its functionality.
Type of PR

[ ] Bug fix
[X] Feature enhancement
[X] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)
https://github.com/dhairyagothi/50_days_50_web_project/assets/136626840/52d24ea9-7433-416b-a452-e21f6886995d
Checklist

[X] I have performed a self-review of my code.
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have followed the code style guidelines of this project.
[X] I have checked for any existing open issues that my pull request may address.
[X] I have ensured that my changes do not break any existing functionality.
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[X] I have read the resources for guidance listed below.
[X] I have followed security best practices in my code changes.

Additional Context
I have designed a logo and created the navbar as per your requirements. The logo replaces the text '50 Days, 50 Web Projects,' and the navbar includes customized hover and other effects using CSS to enhance its interactivity.

done @atharva012004


text:
Dudas - Informe dinámico

Intervalos de tiempo o instantes
En caso de instantes, iniciar en instante 0 (todo vacío) o instante 1
Actualmente, si selecciono una única métrica para el informe, me calcula todas y ya después selecciona la que he elegido. Esto es muy poco óptimo

Intervalos de tiempo o instantes
En caso de instantes, iniciar en instante 0 (todo vacío) o instante 1
Actualmente, si selecciono una única métrica para el informe, me calcula todas y ya después selecciona la que he elegido. Esto es muy poco óptimo

Instantes no intervalos
Instante 0
Esto último no es óptimo corregir


text:
Update DHT11.cpp

Added the convertion of Celsius to Fahrenheit,
Added the convertion of Fahrenheit to Celsius.
Added Heat Index

Let me know if you need any changes to this.

Done


text:
test.py gives ValueError upon EXECUTION

Dear sir,
I am facing the following error as I am trying to run the test.py file. upon execution unity launches for a second and then it closes and gives the following ValueError can you please guide me on how to resolve this problem?
following is the whole data I get after executing the test.py.

(myvenv_unity) C:\Users\Blessing Computer\PPO-algo>python test.py
2022-02-02 01:27:58.717925: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2022-02-02 01:27:58.718621: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
            Using ./training_data/model/train-1/actor_51.hdf5 saved model for testing.

2022-02-02 01:28:13.496256: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library nvcuda.dll
2022-02-02 01:28:13.621982: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:03:00.0 name: GeForce GT 720M computeCapability: 2.1
coreClock: 1.55GHz coreCount: 2 deviceMemorySize: 2.00GiB deviceMemoryBandwidth: 13.41GiB/s
2022-02-02 01:28:13.623311: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2022-02-02 01:28:13.625928: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cublas64_10.dll'; dlerror: cublas64_10.dll not found
2022-02-02 01:28:13.626900: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cufft64_10.dll'; dlerror: cufft64_10.dll not found
2022-02-02 01:28:13.627858: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'curand64_10.dll'; dlerror: curand64_10.dll not found
2022-02-02 01:28:13.628814: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cusolver64_10.dll'; dlerror: cusolver64_10.dll not found
2022-02-02 01:28:13.629776: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cusparse64_10.dll'; dlerror: cusparse64_10.dll not found
2022-02-02 01:28:13.630731: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'cudnn64_7.dll'; dlerror: cudnn64_7.dll not found
2022-02-02 01:28:13.631077: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1753] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2022-02-02 01:28:13.633041: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-02-02 01:28:13.680139: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x21272230490 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2022-02-02 01:28:13.680648: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2022-02-02 01:28:13.683532: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1257] Device interconnect StreamExecutor with strength 1 edge matrix:
2022-02-02 01:28:13.683921: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1263]
WARNING:tensorflow:Error in loading the saved optimizer state. As a result, your model is starting with a freshly initialized optimizer.
WARNING:tensorflow:Model was constructed with shape (None, 54) for input Tensor("observation_input:0", shape=(None, 54), dtype=float32), but it was called on an input with incompatible shape (1, 52).
Traceback (most recent call last):
  File "test.py", line 126, in <module>
    agent.test()
  File "test.py", line 94, in test
    action_probs = self.actor.predict(state, steps=1)  # (1, 2)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py", line 130, in _method_wrapper
    return method(self, *args, **kwargs)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py", line 1599, in predict
    tmp_batch_outputs = predict_function(iterator)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\def_function.py", line 780, in __call__
    result = self._call(*args, **kwds)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\def_function.py", line 823, in _call
    self._initialize(args, kwds, add_initializers_to=initializers)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\def_function.py", line 696, in _initialize
    self._stateful_fn._get_concrete_function_internal_garbage_collected(  # pylint: disable=protected-access
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\function.py", line 2855, in _get_concrete_function_internal_garbage_collected
    graph_function, _, _ = self._maybe_define_function(args, kwargs)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\function.py", line 3213, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\function.py", line 3065, in _create_graph_function
    func_graph_module.func_graph_from_py_func(
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\framework\func_graph.py", line 986, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\eager\def_function.py", line 600, in wrapped_fn
    return weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\framework\func_graph.py", line 973, in wrapper
    raise e.ag_error_metadata.to_exception(e)
ValueError: in user code:
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py:1462 predict_function
        return step_function(self, iterator)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py:1452 step_function
        outputs = model.distribute_strategy.run(run_step, args=(data,))
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:1211 run
        return self._extended.call_for_each_replica(fn, args=args, kwargs=kwargs)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:2585 call_for_each_replica
        return self._call_for_each_replica(fn, args, kwargs)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:2945 _call_for_each_replica
        return fn(*args, **kwargs)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py:1445 run_step  **
        outputs = model.predict_step(data)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\training.py:1418 predict_step
        return self(x, training=False)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\base_layer.py:985 __call__
        outputs = call_fn(inputs, *args, **kwargs)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\functional.py:385 call
        return self._run_internal_graph(
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\functional.py:508 _run_internal_graph
        outputs = node.layer(*args, **kwargs)
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\base_layer.py:975 __call__
        input_spec.assert_input_compatibility(self.input_spec, inputs,
    C:\Users\Blessing Computer\myvenv_unity\lib\site-packages\tensorflow\python\keras\engine\input_spec.py:212 assert_input_compatibility
        raise ValueError(

ValueError: Input 0 of layer fc1 is incompatible with the layer: expected axis -1 of input shape to have value 54 but received input with shape [1, 52]

@dhyeythumar Yes sir I'm also getting the same issue don't know what is the reason behind this value error.

Hi @abiha-inam123 & @BazilaAfridi,
There was minor bug in test.py file, I have fixed it you can check it here

OK, sir thank you so much for your quick response.

Closing this issue as the problem is resolved.

authors: BazilaAfridi abiha-inam123 dhyeythumar


text:
output improvement

[x] compact vs verbose print of explanation chains
[x] dropping shorter/tautological explanation chains

both solved in v1.0

repo: di-unipi-socc/yRCA


text:
action creator to submit the order

Write an action creator to submit the dsc order.
Make a HTTP POST request to the server with order details using appropriate JSON API specification. Upon successful submission, the user will be redirected to a "order submitted successfully" page.

#18

repo: dictyBase/Dicty-Stock-Center


text:
Easier version bump

Automate the process for bumping the extension's version. Can now use npm-version.
npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git]

Closes #36

Try it locally and it works. Thanks for the implementation.
I approved this PR, so please merge when convenient!

repo: dideler/toggle-youtube-comments


text:
Resource Leak

Stream is opened
https://github.com/didi/AoE/blob/ae1cb2ff0249952f1086244060cf0b426b7661b0/linux/src/plugin/AOECrypto.c#L18
Opened file never closed
https://github.com/didi/AoE/blob/ae1cb2ff0249952f1086244060cf0b426b7661b0/linux/src/plugin/AOECrypto.c#L46

line 138 & 215 , too.

authors: Kuloud QiAnXinCodeSafe

repo: didi/AoE


text:
demo：cube-ui/example/pages/radio.vue有错误

原代码：
第十行开始：
<cube-radio-group v-model="selected4">      <cube-radio           v-for="(option, index) in options4"           :key="index"           :option="option">           <img :src="option.src">         </cube-radio>       </cube-radio-group>
其中v-model="selected4" 应该放在cube-radio上，而不是在cube-radio-group

没有错误，在 1.12.11 版本后是支持写在 group 上的。
然后之前的版本是像文档里一样，写在 radio 上的

authors: dolymood lienmac

repo: didi/cube-ui


text:
升级v1.12.27版本后，ScrollNavBar初始化错误

ScrollNavBar初始化时候会出现错误
Property or method "usedTxts" is not defined on the instance

重启也无效吗？从代码上看是存在的

defaultSizes原来是parsed更换成stats后恢复正常了

authors: chinieer dolymood


text:
日志监控采集支持使用通配符或正则来匹配多个日志文件-待认领

建议
您好，在日志采集-日志路径，以后可否能考虑支持日志文件名的通配呢？
如您官网所示，目前只是支持日志末尾自带时间格式，例如 /path/access.log.${%Y%m%d%H}

比如收集nginx日志，有些nginx会担任proxy角色，服务器上也会有多个不同名称的日志文件。此时使用n9e自带的日志采集只能配置多个采集项，不便于迁移到其他节点上。
希望您能予以采纳，多谢。

从产品功能上来看，这个功能可以支持，我把标题改成待认领，希望社区同仁能够贡献PR

每个文件名直接打个标签？

每个文件名直接打个标签？

如果是日期作为后缀，每个小时一个日志文件，会有很多日志文件，tag会约来越多，最终压垮index

清理历史遗留issue，如有问题，请reopen

authors: UlricQin leezer3379 libincla

repo: didi/nightingale


text:
Fix missing ROS_MASTER_URI on master deployment

Change
This PR solves an error while deploying the ROS application on Kubernetes
The ROS_MASTER_URI was not configured on the master node, and therefore a new env var was added to the master deployment.
Issue
While launching the ROS master deployment on Kubernetes, the following error was returned:
/opt/ros/melodic/etc/catkin/profile.d/10.roslaunch.sh: line 3: ROS_MASTER_URI: unbound variable

Care to give this a review? @diegoferigo thanks! :smiley:

Care to give this a review? @diegoferigo thanks! :smiley:

@marcoshuck  The ROS_MASTER_URI variable is exported automatically by the entrypoint.sh:
https://github.com/diegoferigo/ros-kubernetes/blob/316101e906c06ce40993a4398a90ea2ba46b8000/docker/master/entrypoint.sh#L8
I'm not sure exporting this variable is the cleanest way to handle it. I suspect you encountered this problem after entering the container with docker exec [...]. In this case, the entrypoint is not executed and the script is not sourced. Maybe in this case the best solution is sourcing the script in the interpreter configuration (e.g. /etc/bash.bashrc).
My point is that if you don't have that variable defined, your setup is not sourcing the ROS initialization script. Exporting manually the variable will only provide a partially configured setup that could miss something else perhaps in other cases. The best way is always source the script.

@marcoshuck  The ROS_MASTER_URI variable is exported automatically by the entrypoint.sh:
https://github.com/diegoferigo/ros-kubernetes/blob/316101e906c06ce40993a4398a90ea2ba46b8000/docker/master/entrypoint.sh#L8
I'm not sure exporting this variable is the cleanest way to handle it. I suspect you encountered this problem after entering the container with docker exec [...]. In this case, the entrypoint is not executed and the script is not sourced. Maybe in this case the best solution is sourcing the script in the interpreter configuration (e.g. /etc/bash.bashrc).
My point is that if you don't have that variable defined, your setup is not sourcing the ROS initialization script. Exporting manually the variable will only provide a partially configured setup that could miss something else perhaps in other cases. The best way is always source the script.

Hey @diegoferigo, thanks for your response.
I agree it's not the cleaneast solution, but I should mention that I got this problem while initializing the set of pods on my minikube cluster.
That being said, images for those pods were generated as described in the docs using docker-compose build and added to the cluster repository with minikube cache add.
Taking everything into account, I imagine the problem, even if it's related to what you've described, is happening somewhere else.

Hey @diegoferigo, thanks for your response.
I agree it's not the cleaneast solution, but I should mention that I got this problem while initializing the set of pods on my minikube cluster.
That being said, images for those pods were generated as described in the docs using docker-compose build and added to the cluster repository with minikube cache add.
Taking everything into account, I imagine the problem, even if it's related to what you've described, is happening somewhere else.

This problem only happens on the ROS master, and that's not the case for the workers (talker and listener deployments)

This problem only happens on the ROS master, and that's not the case for the workers (talker and listener deployments)

Does it make sense to reproduce this problem to see if I'm the only one who's having it?

Does it make sense to reproduce this problem to see if I'm the only one who's having it?

At the moment I don't have access to a machine in which I can install and configure minikube. Can you make sure that the entrypoint is called in the master deployment? If you browse the logs, you should read the echoed lines:
==> Executing master image entrypoint ...
-> Setting up ROS
==> Container ready

Another attempt could be to inspect the environment that roscore finds before running. I think you can get it printed to the logs by running env && roscore (ported to kubernetes syntax) in the args key:
https://github.com/diegoferigo/ros-kubernetes/blob/316101e906c06ce40993a4398a90ea2ba46b8000/k8s/master-deployment.yaml#L23-L29

At the moment I don't have access to a machine in which I can install and configure minikube. Can you make sure that the entrypoint is called in the master deployment? If you browse the logs, you should read the echoed lines:
==> Executing master image entrypoint ...
-> Setting up ROS
==> Container ready

Another attempt could be to inspect the environment that roscore finds before running. I think you can get it printed to the logs by running env && roscore (ported to kubernetes syntax) in the args key:
https://github.com/diegoferigo/ros-kubernetes/blob/316101e906c06ce40993a4398a90ea2ba46b8000/k8s/master-deployment.yaml#L23-L29

Sure, thanks @diegoferigo, will get back as soon as I have some logs.

Sure, thanks @diegoferigo, will get back as soon as I have some logs.

authors: diegoferigo marcoshuck

repo: diegoferigo/ros-kubernetes


text:
Cargo Audit Fixes

Motivation

Cargo Audit Fix

Test Plan

CI/CD tests are covered

/canary

/canary

:broken_heart: Test Failed - ci-test

:broken_heart: Test Failed - ci-test

Closing this PR due to technical issue, New PR https://github.com/diem/diem/pull/10894

authors: ankitkacn borsdiem

repo: diem/diem


text:
[move-lang][functional-tests] add test cases for friend visibility

call a public(friend) function from friend/non-friend modules
various cyclic dependencies that may be introduced from friend decls

Motivation
Who does not want more tests?
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cargo xtest

I guess so, the tests are lost in the limbo... I'll revive it and do a rebase.

PR revived, rebased to latest main. /land

/land


text:
Add Payment Metadata

Motivation
Adding new metadata type PaymentMetadata as defined in DIP-10. Used for transactions that are specific to payments that can we looked up using a reference ID.
Test Plan
unit test suite

generate code: cargo run -p generate-format -- --corpus diem --record

authors: sunmilee xli


text:
Katalog:datasett bør ikkje vere obligatorisk

At Katalog: datasett er obligatorisk er problematisk i dei tilfeller man ynskjer å publisere ein katalog som består av andre ting enn Dataset, feks DataServices. Eg foreslår derfor at denne egenskapen blir gjort til valgfri.
ref https://doc.difi.no/review/dcat-ap-no/#katalog-datasett

Foreslår at vi ikke endrer her siden DCAT-AP-NO bør være så langt som mulig i samsvar med DCAT-AP.   Kommende BRegDCAT-AP og BRegDCAT-AP-NO dekker derimot behov for "katalog over andre ting enn datasett".

Det er veldig synd. Konsekvensen av dette er i så fall at FDK ikkje vil vere i stand til å etterleve DCAT-AP-NO, sidan vi her baserer oss på kataloger som ikkje inneholder dataset, men kun DataServices. API-katalogen er eit døme på katalog som ikkje har datasets.
Datasets ligg i andre kataloger. Dette følger "naturlig" av at vi altså har skilt API-katalogen (dataservices) ut som ein eigen katalog, ikkje som ein eigenskap til datasett.

Dette vil antageligvis også potensielt ramme dei som hadde planar om å bruke dcat-ap-no v2 til å dele api ut av api-management løysingar, der datasett truleg er dokumentert andre stader.

BRegDCAT-AP-NO skal jo kunne brukes av de som skal ha kataloger som ikke (nødvendigvis) inneholder datasett (f.eks. API-katalogen i FDK).

Lukker denne (ref. møtet i dag 22/4).

authors: jimjyang stigbd

repo: difi/dcat-ap-no


text:
chore: don't delete own data when leaving a project

When you leave a project, we no longer delete your own data (but still
close your writer Hypercore).
Because this was the last occurrence of deleteOwn: false, I removed
the option entirely.
Fixes #449.

I'll plan to merge this tomorrow morning unless there are any objections.

repo: digidem/mapeo-core-next


text:
Download link is broken

http://digilist.de/snakedumper.phar redirects to https://digilist.de/digilist.de which responds with a 404 error code.

Even https://digilist.de and https://digilist.de/snakedumper.phar behave as explained above. Is it maybe a web server misconfiguration?

Hey Robert, thanks for reporting this. I fixed my webserver, the download is now available again.

authors: digilist robertfausk

repo: digilist/SnakeDumper


text:
"ota sign" not available

In the readme:
"4. Sign the file after you've verified it's good: vector-web-setup ota-sign"
raises error: unknown command 'ota-sign'. See 'vector-web-setup --help'
"vector-web-setup --help" shows no command called "ota-sign", see screenshot

You are right it should be ota-approve. I have made the necessary change.

This was a documentation error and the README has been updated.

authors: anant-kaushik grant-olson xanathon

repo: digital-dream-labs/vector-web-setup