influxdb continuously restarts itself

Bug report
System info:
hostnamectl
   Static hostname: xxx
         Icon name: computer-server
           Chassis: server
        Machine ID: 559d1565d56443aeb5945716689b8dff
           Boot ID: 460a89ed9b2a4fdd9db654c17f29bedd
  Operating System: CentOS Linux 7 (Core)
       CPE OS Name: cpe:/o:centos:centos:7
            Kernel: Linux 3.10.0-514.26.2.el7.x86_64
      Architecture: x86-64

influxd: [I] 2017-11-03T14:10:48Z InfluxDB starting, version 1.3.5, branch HEAD, commit 9d9001036d3585cf21925c13a57881bc6c8dcc7e
influxd: [I] 2017-11-03T14:10:48Z Go version go1.8.3, GOMAXPROCS set to 32

Steps to reproduce:

writing multiple datapoints in the wire protocol format using the HTTP API

Expected behavior:
db not to restart itself
Actual behavior:
db restarts every 30s or so
Additional info:

config

# cat /etc/influxdb/influxdb.conf | egrep -v '#' | egrep -v '^$'
reporting-disabled = true
bind-address = "x.x.x.x:8088"
[meta]
  dir = "/var/lib/influxdb/meta"
[data]
  dir = "/usr/ip-spotlight/influxdb/data"
  wal-dir = "/usr/ip-spotlight/influxdb/wal"
  wal-fsync-delay = "1s"
  index-version = "tsi1"
  max-series-per-database = 0
  max-values-per-tag = 0
[coordinator]
[retention]
  check-interval = "60m"
[shard-precreation]
  check-interval = "10m"
[monitor]
[http]
  bind-address = "x.x.x.x:8086"
  auth-enabled = true
[subscriber]
[[graphite]]
[[collectd]]
[[opentsdb]]
[[udp]]
[continuous_queries]
  run-interval = "60m"

/var/log/messages

Nov  3 15:14:11 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:11Z Listening on HTTP:x.x.x.x:8086 service=httpd
Nov  3 15:14:11 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:11Z Starting retention policy enforcement service with check interval of 1h0m0s service=retention
Nov  3 15:14:11 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:11Z Listening for signals
Nov  3 15:14:12 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:12Z beginning level 2 compaction of group 0, 3 TSM files engine=tsm1
Nov  3 15:14:12 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:12Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000002-000000002.tsm (#0) engine=tsm1
Nov  3 15:14:12 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:12Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000001.tsm (#1) engine=tsm1
Nov  3 15:14:12 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:12Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000002.tsm (#2) engine=tsm1
Nov  3 15:14:16 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:16+01:00" level=info msg=Request component=server method=GET remote_addr="<IP_ADDRESS>:13512" url=/chronograf/v1/me
Nov  3 15:14:16 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:16+01:00" level=info msg="Response: OK" code=200 component=server remote_addr="<IP_ADDRESS>:13512" response_time="93.66µs"
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: panic: runtime error: slice bounds out of range
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: goroutine 46 [running]:
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*SeriesBlock).UnmarshalBinary(0xc4bd9fd400, 0x7f10a29f0004, 0x8f86fb29, 0x8f86fb29, 0x8f86fb2d, 0x0)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:185 +0x8cf
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.mapIndexFileSeriesBlockFile(0xc42000e028, 0x4f, 0x1000, 0x4f, 0x0, 0x0, 0x4f)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:983 +0xd6
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.mapIndexFileSeriesBlock(0xeab4e0, 0xc42000e028, 0x0, 0xea7ea0, 0xc4412a0080, 0x2000000, 0x6, 0xc420065150)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:954 +0x1bc
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.IndexFiles.CompactTo(0xc4266549e8, 0x2, 0x3, 0xeab4e0, 0xc42000e028, 0x2000000, 0x6, 0x8f86fb2d, 0x0, 0x0)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index_files.go:154 +0x2e6
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compactToLevel(0xc42011a540, 0xc4266549e8, 0x2, 0x3, 0x2)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:926 +0x8ed
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compact.func1.1(0xc42011a540, 0xc4266549e8, 0x2, 0x3, 0x1)
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:879 +0x8e
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: created by github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compact.func1
Nov  3 15:14:23 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:888 +0x8b
Nov  3 15:14:23 at-vie01a-ispacc02 systemd: influxdb.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov  3 15:14:23 at-vie01a-ispacc02 systemd: Unit influxdb.service entered failed state.
Nov  3 15:14:23 at-vie01a-ispacc02 systemd: influxdb.service failed.
Nov  3 15:14:24 at-vie01a-ispacc02 systemd: influxdb.service holdoff time over, scheduling restart.
Nov  3 15:14:24 at-vie01a-ispacc02 systemd: Started InfluxDB is an open-source, distributed, time series database.
Nov  3 15:14:24 at-vie01a-ispacc02 systemd: Starting InfluxDB is an open-source, distributed, time series database...
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 8888888           .d888<PHONE_NUMBER>b.  888888b.
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888            d88P"  888                   888  "Y88b 888  "88b
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888            888    888                   888    888 888  .88P
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888   88888b.  888888 888 888  888 888  888<PHONE_NUMBER>888K.
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888   888 "88b 888    888 888  888  Y8bd8P' 888    888 888  "Y88b
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888   888  888 888    888 888  888   X88K   888    888 888    888
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 888   888  888 888    888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: 8888888 888  888 888    888  "Y88888<PHONE_NUMBER>888P"  8888888P"
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z InfluxDB starting, version 1.3.5, branch HEAD, commit 9d9001036d3585cf21925c13a57881bc6c8dcc7e
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z Go version go1.8.3, GOMAXPROCS set to 32
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z Using configuration at: /etc/influxdb/influxdb.conf
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z Using data dir: /usr/ip-spotlight/influxdb/data service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/5/000000002-000000002.tsm (#0) opened in 303.09µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/9/000000003-000000002.tsm (#0) opened in 343.067µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/8/000000003-000000002.tsm (#0) opened in 284.054µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/9/_00047.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/5/_00043.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/8/_00046.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/10/000000003-000000002.tsm (#0) opened in 1.261443ms engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/10/_00047.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/11/000000004-000000002.tsm (#0) opened in 546.084µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/6/000000002-000000002.tsm (#0) opened in 671.307µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/11/_00047.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/6/_00044.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/7/000000002-000000002.tsm (#0) opened in 332.963µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/9 opened in 15.013416ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/5 opened in 15.307165ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/7/_00045.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/8 opened in 15.472613ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/13/000000001-000000001.tsm (#0) opened in 366.623µs engine=tsm1 service=filestore
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00005.wal, size 10494060 engine=tsm1 service=cacheloader
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/6 opened in 16.750112ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/10 opened in 16.566412ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/7 opened in 16.671532ms service=store
Nov  3 15:14:24 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:24Z /usr/ip-spotlight/influxdb/data/_internal/monitor/11 opened in 16.707842ms service=store
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00006.wal, size 9131003 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00007.wal, size 11429 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00008.wal, size 11476 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00009.wal, size 11550 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00011.wal, size 11448 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00012.wal, size 22942 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00013.wal, size 11432 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00014.wal, size 11406 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00015.wal, size 11474 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00021.wal, size 11625 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00022.wal, size 11568 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00023.wal, size 11442 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00024.wal, size 11449 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00025.wal, size 11356 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00027.wal, size 11387 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00028.wal, size 11397 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00029.wal, size 11319 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00030.wal, size 11450 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00031.wal, size 11518 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00035.wal, size 11411 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00036.wal, size 11406 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00038.wal, size 11430 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00039.wal, size 11558 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z reading file /usr/ip-spotlight/influxdb/wal/_internal/monitor/13/_00041.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z /usr/ip-spotlight/influxdb/data/_internal/monitor/13 opened in 1.457648511s service=store
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z performing full compaction index=tsi token=6fdba7 src=182,173 dst=/usr/ip-spotlight/influxdb/data/pmacct/1w/14/index/L4-00000302.tsi
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z performing full compaction index=tsi token=16c046 src=123,94 dst=/usr/ip-spotlight/influxdb/data/pmacct/1w/14/index/L5-00000304.tsi
Nov  3 15:14:25 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:25Z performing full compaction index=tsi token=38c338 src=151,52 dst=/usr/ip-spotlight/influxdb/data/pmacct/1w/14/index/L6-00000305.tsi
Nov  3 15:14:26 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:26+01:00" level=info msg=Request component=server method=GET remote_addr="<IP_ADDRESS>:13512" url=/chronograf/v1/me
Nov  3 15:14:26 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:26+01:00" level=info msg="Response: OK" code=200 component=server remote_addr="<IP_ADDRESS>:13512" response_time="67.859µs"
Nov  3 15:14:26 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:26Z performing full compaction index=tsi token=997291 src=229,228 dst=/usr/ip-spotlight/influxdb/data/pmacct/1w/14/index/L2-00000303.tsi
Nov  3 15:14:26 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:26Z /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000002.tsm (#2) opened in 566.640798ms engine=tsm1 service=filestore
Nov  3 15:14:26 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:26Z /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000001.tsm (#1) opened in 982.615479ms engine=tsm1 service=filestore
Nov  3 15:14:26 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:26Z /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000002-000000002.tsm (#0) opened in 984.369571ms engine=tsm1 service=filestore
Nov  3 15:14:26 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:26Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00058.wal, size 10487608 engine=tsm1 service=cacheloader
Nov  3 15:14:27 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:27Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00059.wal, size 10494565 engine=tsm1 service=cacheloader
Nov  3 15:14:27 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:27Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00060.wal, size 10583870 engine=tsm1 service=cacheloader
Nov  3 15:14:28 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:28Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00061.wal, size 2706567 engine=tsm1 service=cacheloader
Nov  3 15:14:28 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:28Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00062.wal, size 4353039 engine=tsm1 service=cacheloader
Nov  3 15:14:28 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:28Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00064.wal, size 3910941 engine=tsm1 service=cacheloader
Nov  3 15:14:28 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:28Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00070.wal, size 3539194 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00071.wal, size 3581887 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00072.wal, size 1050541 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00076.wal, size 78490 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00086.wal, size 5119030 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00087.wal, size 2385686 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00093.wal, size 328288 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00094.wal, size 1227713 engine=tsm1 service=cacheloader
Nov  3 15:14:29 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:29Z reading file /usr/ip-spotlight/influxdb/wal/pmacct/1w/14/_00096.wal, size 0 engine=tsm1 service=cacheloader
Nov  3 15:14:36 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:36+01:00" level=info msg=Request component=server method=GET remote_addr="<IP_ADDRESS>:13512" url=/chronograf/v1/me
Nov  3 15:14:36 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:36+01:00" level=info msg="Response: OK" code=200 component=server remote_addr="<IP_ADDRESS>:13512" response_time="84.433µs"
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z /usr/ip-spotlight/influxdb/data/pmacct/1w/14 opened in 18.314356391s service=store
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z opened service service=subscriber
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting monitor system service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z 'build' registered for diagnostics monitoring service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z 'runtime' registered for diagnostics monitoring service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z 'network' registered for diagnostics monitoring service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z 'system' registered for diagnostics monitoring service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting precreation service with check interval of 10m0s, advance period of 30m0s service=shard-precreation
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting snapshot service service=snapshot
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting continuous query service service=continuous_querier
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting HTTP service service=httpd
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Authentication enabled:true service=httpd
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Storing statistics in database '_internal' retention policy 'monitor', at interval 10s service=monitor
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Listening on HTTP:x.x.x.x:8086 service=httpd
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Starting retention policy enforcement service with check interval of 1h0m0s service=retention
Nov  3 15:14:42 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:42Z Listening for signals
Nov  3 15:14:43 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:43Z beginning level 2 compaction of group 0, 3 TSM files engine=tsm1
Nov  3 15:14:43 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:43Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000002-000000002.tsm (#0) engine=tsm1
Nov  3 15:14:43 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:43Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000001.tsm (#1) engine=tsm1
Nov  3 15:14:43 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:14:43Z compacting level 2 group (0) /usr/ip-spotlight/influxdb/data/pmacct/1w/14/000000003-000000002.tsm (#2) engine=tsm1
Nov  3 15:14:46 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:46+01:00" level=info msg=Request component=server method=GET remote_addr="<IP_ADDRESS>:13512" url=/chronograf/v1/me
Nov  3 15:14:46 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:46+01:00" level=info msg="Response: OK" code=200 component=server remote_addr="<IP_ADDRESS>:13512" response_time="74.839µs"
Nov  3 15:14:56 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:56+01:00" level=info msg=Request component=server method=GET remote_addr="<IP_ADDRESS>:13512" url=/chronograf/v1/me
Nov  3 15:14:56 at-vie01a-ispacc02 chronograf: time="2017-11-03T15:14:56+01:00" level=info msg="Response: OK" code=200 component=server remote_addr="<IP_ADDRESS>:13512" response_time="358.943µs"
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: panic: runtime error: slice bounds out of range
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: goroutine 31 [running]:
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*SeriesBlock).UnmarshalBinary(0xc4fcaa8980, 0x7f7c10734004, 0x8f86fb29, 0x8f86fb29, 0x8f86fb2d, 0x0)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:185 +0x8cf
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.mapIndexFileSeriesBlockFile(0xc42136e000, 0x4f, 0x1000, 0x4f, 0x0, 0x0, 0x4f)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:983 +0xd6
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.mapIndexFileSeriesBlock(0xeab4e0, 0xc42136e000, 0x0, 0xea7ea0, 0xc432c102c0, 0x2000000, 0x6, 0xc420063150)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/series_block.go:954 +0x1bc
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.IndexFiles.CompactTo(0xc4358f60e8, 0x2, 0x3, 0xeab4e0, 0xc42136e000, 0x2000000, 0x6, 0x8f86fb2d, 0x0, 0x0)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index_files.go:154 +0x2e6
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compactToLevel(0xc4203621c0, 0xc4358f60e8, 0x2, 0x3, 0x2)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:926 +0x8ed
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compact.func1.1(0xc4203621c0, 0xc4358f60e8, 0x2, 0x3, 0x1)
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:879 +0x8e
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: created by github.com/influxdata/influxdb/tsdb/index/tsi1.(*Index).compact.func1
Nov  3 15:15:02 at-vie01a-ispacc02 influxd: /root/go/src/github.com/influxdata/influxdb/tsdb/index/tsi1/index.go:888 +0x8b
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: influxdb.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: Unit influxdb.service entered failed state.
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: influxdb.service failed.
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: influxdb.service holdoff time over, scheduling restart.
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: Started InfluxDB is an open-source, distributed, time series database.
Nov  3 15:15:03 at-vie01a-ispacc02 systemd: Starting InfluxDB is an open-source, distributed, time series database...
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 8888888           .d888<PHONE_NUMBER>b.  888888b.
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888            d88P"  888                   888  "Y88b 888  "88b
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888            888    888                   888    888 888  .88P
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888   88888b.  888888 888 888  888 888  888<PHONE_NUMBER>888K.
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888   888 "88b 888    888 888  888  Y8bd8P' 888    888 888  "Y88b
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888   888  888 888    888 888  888   X88K   888    888 888    888
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 888   888  888 888    888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: 8888888 888  888 888    888  "Y88888<PHONE_NUMBER>888P"  8888888P"
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:15:03Z InfluxDB starting, version 1.3.5, branch HEAD, commit 9d9001036d3585cf21925c13a57881bc6c8dcc7e
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:15:03Z Go version go1.8.3, GOMAXPROCS set to 32
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:15:03Z Using configuration at: /etc/influxdb/influxdb.conf
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:15:03Z Using data dir: /usr/ip-spotlight/influxdb/data service=store
Nov  3 15:15:03 at-vie01a-ispacc02 influxd: [I] 2017-11-03T14:15:03Z /usr/ip-spotlight/influxdb/data/_internal/monitor/10/000000003-000000002.tsm (#0) opened in 148.758µs engine=tsm1 service=filestore

This log message looks suspicious (included above):
influxd: panic: runtime error: slice bounds out of range

@nskalis I haven't seen that issue before. Are you able to provide the index directories? I can take a take a look and try to see what's going on.

hi. i am sorry. but i deleted the data and wal directories, and issue disappeared.
then i tried to write some data; (1) if i was using more than 1 processes i was getting error 500 (2) doing batch inserts was producing the following:
2017-11-03 17:54:52,613 | INFO | 107673 | datastore | write_data_into_influxdb | getting http response status code `500` when writing data in influxdb `pmacct`
2017-11-03 17:55:05,918 | INFO | 107673 | datastore | write_data_into_influxdb | getting http response status code `500` when writing data in influxdb `pmacct`
2017-11-03 17:55:19,045 | INFO | 107673 | datastore | write_data_into_influxdb | getting http response status code `400` when writing data in influxdb `pmacct`
2017-11-03 17:55:32,138 | INFO | 107673 | datastore | write_data_into_influxdb | getting http response status code `204` when writing data in influxdb `pmacct`
2017-11-03 17:55:45,482 | INFO | 107673 | datastore | write_data_into_influxdb | getting http response status code `500` when writing data in influxdb `pmacct`

which seemed to be non-deterministic output.
i have un-installed influxdb..

@nskalis if you deleted the directories without issuing the appropriate commands to the database, i.e., DROP DATABASE xyz then the server is going to be in a bit of a state. I would issue the appropriate DROP commands and restart the server.

@e-dard no. i did delete the contents of the data and wal directories, after influxdb was continuously failing (and not the other way around).

@nskalis have you tried upgrading to 1.4.2 and are you still experiencing this issue?

@nskalis -- we haven't heard back from you on this issue.  Is this still something you want to investigate or shall we close this out?

Hi please feel to close the issue.

On 29 Mar 2018, at 19:00, timhallinflux<EMAIL_ADDRESS>wrote:
@nskalis -- we haven't heard back from you on this issue. Is this still something you want to investigate or shall we close this out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Is there a screenshot or example of what a status looks like?

I might be really silly but I tried implementing this and couldn't get anything to show up in checks. I wanted to make a link to a deployed URL following this pattern https://github.com/jsmrcaga/action-netlify-deploy#use-branch-name-to-deploy
The action is passing but I cannot see the status.

I messed up the pull request part 🤦♂. Thanks for this awesome action.
What fixed my problem, maybe this could be the default?
          sha: ${{github.event.pull_request.head.sha || github.sha}}

Hi thanks for the feedback.
I am not sure if changing this default would be breaking for existing users who don't have this triggering on a pull.
I would have to write up a test to find out, currently my project plate is full but I'll add it as a TODO.


When starting a slideshow the program gets stuck on Error Dialog about labeling all tags

If one adds an annotation and doesn't assign a label to it, the program will issue an Error Dialog when trying to move on to the next frame, stating that all tags have to be labeled first.
When pressing the Play Button to automatically advance the frames (slideshow mode) the program won't allow to leave this error dialog window, thereby blocking the application in total, only beeing able to exit by process killing. This is probably beeing caused by the timer for slideshow which isn't interrupted in case of an error (e.g. not all tags labelled).
I think it is also noteworthy to discuss if really every tag should be labelled or in other words if this really justifies for an error which blocks the user from advancing the images or if this rather should be a warning popping up, without requiring further user interaction (e.g. clicking away the error message).

I just noted, that this only happens when in image directory mode (not when working with a video file).
All in all the behaviour for this is inconsistent, since it is possible to advance to another frame when clicking on the timeline (also if not all tags are labelled) but the same is not possible when using the sequence controll buttons (next frame).


App title and app bar links in navigation drawer layout are only visible on small screens

The app title and app bar links only appear when you reduce the width until the navigation drawer becomes modal.
To Reproduce
Add app title and app bar links, reduce width of browser window until they appear.
Expected behaviour
They would always be visible.

This is when importing m3 as a dependency to an existing app. When I create a fresh m3 app, it does not seem like the app title and app bar link slots are available. Perhaps this is work in process that was not supposed to be available yet :)

I believe this is intended functionality - see #227


GEOMETRY-94: PlaneConvexSubset implementations

adding additional PlaneConvexSubset subtypes: ConvexPolygon3D and Triangle3D
simplifying core Plane class by removing u and v vectors and placing into EmbeddingPlane subclass
adding Bounds2D and Bounds3D classes (GEOMETRY-77)

Merged in commit ed41804dc3f8273e483ddfabd331732e1ae2c550


Title improvements

Title improvements:
Refs: https://github.com/TryGhost/Ghost/issues/8191
Closes: https://github.com/TryGhost/Ghost/issues/8292

Clean up the connection between the editor and title.
Encapsulate all title related events in the title component.
Fixes tab support
Makes sure that the empty title psuedo-element is below the cursor.
Makes sure that a blank title always displays the psuedo-element.

Coverage decreased (-0.4%) to 73.914% when pulling 8ca00893190803e4c3f0b73be12be558987ba3fd on disordinary:title-integration into 4d2441873f595f9795ab1ae50ba061ddcc1e6dd2 on TryGhost:master.

Coverage decreased (-0.4%) to 73.92% when pulling 67e7b28c1e200a89fbbe52b23e94d86cb8c5ff15 on disordinary:title-integration into 3d84e01318a8948e58285db1bcf3f22c3e521036 on TryGhost:master.

Coverage decreased (-0.4%) to 73.937% when pulling d1920354817142f9fb405156ead9a4b1becd2b45 on disordinary:title-integration into 3d84e01318a8948e58285db1bcf3f22c3e521036 on TryGhost:master.

Coverage decreased (-0.4%) to 73.937% when pulling 20e5d78922e2c289e6c563aae2072830a042b58f on disordinary:title-integration into 3d84e01318a8948e58285db1bcf3f22c3e521036 on TryGhost:master.


Add extensions_rag_on_edge_multimodal - Drop Submission

This is a multi-modal (image + text) Retrieval-Augmented Generation(RAG) on edge pattern that facilitates multi-modal text and image searches within files utilizing a multi-modal vector search engine Marqo and an multi-modal Large Language Model LLaVa.
The tool can help on machine troubleshooting on-site.
The solution is independent from cloud services, and can be deployed to the edge device.

@ChenCheng368 please review my comments. Let me know if you have questions.

@fcabrera23 , I've committed the updates with your comments, please help to review again, thanks!


Term of Use

We would like to use your service, but unfortunately the Terms of Use are not very user friendly (https://gist.github.com/CLAassistant/3a73e4cd729c9d0a6e30).
Particularly section 4:
By transmitting or uploading any Content (defined below) to the Website, You grant to SAP a perpetual, irrevocable, nonexclusive, worldwide, fully paid up and royalty free, unlimited license to use such Content without restrictions of any kind and without any payment or other consideration of any kind, or permission or notification to You or any third party.
The license includes, without limitation, the irrevocable right to reproduce, prepare derivative works, combine with other works, alter, translate, distribute copies, display, perform, license the Content, and all rights therein; to make, have made, offer to sell, sell, lease, or otherwise distribute any Content or product; and to practice any method, embodying such Content (including the right to sublicense any of the foregoing).
When contributors submit personal information such as name, email, address, phone number, etc. in good faith the information submitted will remain private, these Terms of Use in fact allow SAP SE to publish them (among other things).
Do you have any plans to change this?
It would be great, as CLA assistant is otherwise a great tool.

We have reached out to our legal team to check this. Thanks for mentioning that.

Any update on this?

Not yet.. vacation time.

We have now updated our TOS according to your feedback. We hope that you are now able to use our service.
https://gist.github.com/CLAassistant/3a73e4cd729c9d0a6e30

That's awesome! Thanks @thojansen :) Once we are going to verify it with our legal team.. we'll let you know..


Add E2E Testing.

The project has unit testing with jest. However, there is no E2E testing.

Check list

[x] Migrate webpack bindler to Vite
[x] Setup Vitest
[x] Setup Playwright
[x] Setup Github Actions
[ ] Add more tests


Dimensions fix for retrieving voxel properties

Description
After the commit https://github.com/PolarizedLightFieldMicroscopy/GeoBirT/commit/cbda36702f2d14321b06af416b769b4f2d26579b, modifying the for-loop for matrix multiplication, the reconstruction process fails when using only the restricted set of parameters.
Screenshots

Files
https://github.com/PolarizedLightFieldMicroscopy/GeoBirT/blob/cbda36702f2d14321b06af416b769b4f2d26579b/src/VolumeRaytraceLFM/birefringence_implementations.py#L2149-L2151
To Reproduce
Run the function recon_voxel() which includes the command reconstructor.reconstruct(all_prop_elements=False).
Tasks

[ ] Inspect the dimensions of volume.optic_axis_planar. I do know why this variable is different than volume.optic_axis_active.
[ ] Add a pytest that tests this aspect of the reconstruction process. This issue currently exists even though all current tests pass.

I found that running reconstructor.reconstruct(all_prop_elements=True) also failed because some properties were undefined. However, setting recon_config.interation_parameters["two_optic_axis_components"] = False before creating the reconstructor allowed the reconstruction process to run properly. We still also want to be able to reconstruct from just the two optic axis components.

This line of code is actually causing the error first:
https://github.com/PolarizedLightFieldMicroscopy/GeoBirT/blob/cbda36702f2d14321b06af416b769b4f2d26579b/src/VolumeRaytraceLFM/birefringence_implementations.py#L2146-L2148
Relevant dimensions

Fixed by 5c7bdabcf3f9022348e700079c8f9dbec7ec37c3


[5d] pkg: create a script to build pkg on macOS locally

[ ] Define locations
[ ] Plist file to create service
[ ] Uninstall script
[ ] Pre install script (clear after brew installation)

[ ] Design wizard steps
[ ] Pack everything with pkg(tool)
[ ] Verify that we check version of macOS to be supported one (warning or block install, check with @josemore)
[ ] Sudo?

extra

[ ] Integrate nri-flex binary and config samples
[ ] Sign nri-flex binary

refs:

http://bomutils.dyndns.org/tutorial.html
https://www.manpagez.com/man/1/pkgutil/
https://medium.com/swlh/the-easiest-way-to-build-macos-installer-for-your-application-34a11dd08744
https://stackoverflow.com/questions/40993048/how-to-enforce-mac-package-installer-to-check-version
more details: https://github.com/newrelic/infrastructure-agent/issues/721

Not a short-term priority


Fix playwright.is_enabled to actually call options.is_enabled

Don't return if the test-file pattern matches.

@flunderpero ooops, thanks for the fix!


Issue 101 cicd

@jcilacad  Please create a personal access token with package privileges if you hadn't already and add it as REGISTRY_TOKEN secret. After that, merge this pull request to check the automated flow so far

Done.


Implement BIP 101 and accurate sigop/sighash counting

Patches against the final 0.11 Core release that implement BIP 101 and implement accurate sigop/sighash counting (as described in draft BIP that hasn't been assigned a number yet).

Did any of the earlier patches change too, or can I assume my old reviews are still valid for them?

Earlier patches are exactly the same, just rebased against the final Core 0.11 release.

Updated last commit with better comments in response to @mikehearn review.

My thinking around the check limit was, what if someone mines an invalid block with an overlimit transaction. In this case there will be a check against the limits every 8 megabytes of data serialized and hashed. If we end up hashing 8MB too much, then it seems like no big deal. As block size goes up the "slack" by which we might verify too much data goes up though, and then the limit can't be made really hard without another consensus rule change. We could end up hashing 16MB too much data (or more, if done in parallel).
However I guess a lot of the overhead is actually not the hashing but rather the serialization. So serializing, then checking the size of the serialised data against the limits, then hashing that, maybe it doesn't save enough time to be worthwhile.
I'll merge this into the only-bigblocks branch and master, and kick off some builds.

This was merged and launched already.


Correct settings for rssi Steele pdb

Hi there.
I've been following the few videos online and tutorials of how to setup the rssi to show up in my osd and so far I've gotten it to show up but I get 0-1db. Does that mean that perhaps my scale in the config tool isn't set correctly ? I have it currently set to 1009-2000 and the mixer on my taranis is weight 100 scale 0.
Tanks in advance

Did you double check the RSSI section here:
https://github.com/awolf78/KISS_OSD/wiki#setup-of-kiss-osd

Hi there,
yes I did review it.
If i mess around with the weight and offset in the mixer page of my radio i
can see receiving signal but goes int negative and it doesnt make any sense.
https://newbeedrone.com/products/frsky-2-4ghz-xsr
Here is a link to the receiver I am using currently. In the forum they
mention to flash the firmware if the xm+ is being used. I didnt find that
necessary since im using a different receiver but maybe that is the case.
Could you confirm if that would be something for me to try or not ? I dont
want to try and flash my receiver and get it damaged.
I played around with the setting of the kiss osd and that didnt change
anything. The FC sees the input and reads it as a value between 1000-2000
ppm but I dont know where is the missing link. My radio sees the rssi. The
Flight controller does as well, however the osd can see it in negative
value if I do weight 200 and offset -100 but the numbers dont make any
sense.
Best regards,
Rumen
On Sat, Dec 8, 2018 at 4:49 AM awolf78<EMAIL_ADDRESS>wrote:

Did you double check the RSSI section here:
https://github.com/awolf78/KISS_OSD/wiki#setup-of-kiss-osd
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/awolf78/KISS_OSD/issues/58#issuecomment-445456790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Arl6TdDwTUltiNSCuFP4gP4R2Iccs1HOks5u27VBgaJpZM4ZJjlz
.

Can you post a DVR or video of what is happening?

Yes I will try to do it today or tomorrow. Thanks for the prompt response.

Rumen

On Sun, Dec 9, 2018 at 3:03 PM awolf78<EMAIL_ADDRESS>wrote:

Can you post a DVR or video of what is happening?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/awolf78/KISS_OSD/issues/58#issuecomment-445580419,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Arl6TcIpeR8C4GHzqghkobp0ZJbRXbhMks5u3Za4gaJpZM4ZJjlz
.


Make Maven Artifact cache configrable

What needs to be done
Make Maven artifact cache configurable by setting an application property.
Read from Maven Repository but download new dependencies to separate Maven cache (current)
new MavenArtifactDownloader(
                        ReadOnlyLocalMavenArtifactCache.mavenLocal().orElse(
                            new LocalMavenArtifactCache(Paths.get(System.getProperty("user.home"), ".rewrite", "cache", "artifacts")

Use local Maven repository for reading and writing
new MavenArtifactDownloader(new LocalMavenArtifactCache(Paths.get(System.getProperty("user.home"), ".m2", "repository")), ...

Why it needs to be done
It can be useful (and easier to understand) if all dependencies are stored and retrieved from the local Maven repository but then SBM potentially overwrites dependencies in the local Maven repository.
Allow a user to choose.
Additional Information
See DependencyHelper.downloadArtifacts(...) for artifact configuration and ApplicationProperties for properties

@fabapp2 I would like to take this up.

@fabapp2 I would like to take this up.
Hi @ravig-kant,
that would be awesome, thanks for your interest!

Please sign the Contributor License Agreement beforehand, if you haven't already done so.
I just checked again and realized it will require some refactoring to make DependencyHelper a spring-managed bean as it's currently created using new. If you don't mind, it would be helpful as a first step to just try to implement the switch inside DependencyHelper depending on the property, e.g. sbm.onlyUseLocalMavenRepository (or a better name) and then I/we see how the DependencyHelper can be made a spring-managed bean in a second step?
The relevant branch (e.g. with related TODO in DependencyHelper) is upgrade-rewrite-7.18.2 which I am working on atm. Please create a new branch from this branch in your fork so we can use this for discussion.
Please also have a look at OpenRewriteMavenBuildFileTest.testResolvedDependenciesWithPomTypeDependency()
where this problem surfaced to me. In this test, I hacked something to deal with the current implementation. This could be changed afterward to use the new "Use local Maven repository for reading and writing" configuration.
Basically by adding matching application properties like this
TestProjectContext.buildProjectContext()
                .withApplicationProperties(...)
                ...

Which would allow to remove the hack in OpenRewriteMavenBuildFileTest.testResolvedDependenciesWithPomTypeDependency
if(dep.contains(".rewrite/cache/artifacts/")) {
                        return dep.substring(dep.lastIndexOf(".rewrite/cache/artifacts/") + ".rewrite/cache/artifacts/".length());
                    } else {

If everything works and we found a way how to make DependencyHelper a spring-bean, a section in applications/spring-shell/src/main/resources/banner.txt describing the functionality and the current property setting would be nice.
If you have questions or need help, please don't hesitate to ask.

Thanks for the detailed explanation. Actually, I started working on making DependencyHelper a spring bean before your email. I should have replied earlier, but I got caught up in some personal work.
The approach I took was to create an inner class Builder in ClasspathRegistry and make it a spring Bean.  DependencyHelper will be autowired in the Builder. The Builder then uses the injected DependencyHelper to initDependency in the ClasspathRegistry.
ClasspathRegistry instance is created by OpenRewriteMavenBuildFile which is instantiated from spring beans. So I thought of injecting ClasspathRegistry.Builder to OpenRewriteMavenBuildFile.
Please let me know whether this approach is correct. Otherwise, I will use a simple property-based approach for now. I am almost halfway through with changes. I can quickly add it to my fork so that you can review the code. It would be much easier to understand the approach by looking at the code.

Pushing it into your fork would be helpful. I think I vaguely understood but looking at the code would ease our conversation.
If you like you could also create a draft P R and we discuss it there. Both work for me. Please be aware that I will be ooo from  11th for 7 days. Will check tomorrow, otherwise when I'm back

Hi @fabapp2
I pulled the latest branch, and it seems that my original idea of introducing the Builder requires another round of thinking with new changes. For example, the earlier version didn't have JavaParsers and Current and Initial dependencies concepts.
In a week, I will either come up with a proposal on how to make Dependency Helper a spring bean or have a PR with a simple property. I want to use this opportunity to learn about the code to contribute more in the future.

Hi @ravig-kant
I am happy about your interest and any contribution is appreciated!
While working on the upgrade to OpenRewrite 7.23.0 I realized some changes that will probably affect your work, I'm afraid might have been tagging this as 'good-first-issue' a bit too fast.
Nevertheless, I would be glad to have you contribute but unfortunately there are a few issues that need to be solved first to not waste your precious time on this. Maybe you want to pick something else for now, or maybe just wait until I'm back from PTO next week?
This needs to be sorted out:

Quite a few things changed related to Maven and dependency resolution since 7.17.3 which is the Rewrite version currently on main
OpenRewrite's AddDependency recipe can now download added dependencies
Being able to replace SBM's AddDependency recipe with OR's would make the DependencyHelper used in OpenRewriteMavenBuildFile.addDependenc obsolete as it's used to download dependencies added to the pom.xml
Then the MavenArtifactDownloader wouldn't be used in DependencyHelper anymore
But OR's AddDependency requires a type in use onlyIfUsing to be effective. In SBM the type must be added after adding the dependency
To switch between the two modes (rewrite cache or Maven cache) the MavenArtifactCache used in MavenArtifactDownloader needs to be reconfigured/changed by an application property
MavenArtifactDownloader is currently only used in MavenProjectParser when initially parsing the project
Q: Is the MavenArtifactDownloader used to download dependencies?

Hi @fabapp2
I pulled the latest branch, and it seems that my original idea of introducing the Builder requires another round of thinking with new changes. For example, the earlier version didn't have JavaParsers and Current and Initial dependencies concepts. In a week, I will either come up with a proposal on how to make Dependency Helper a spring bean or have a PR with a simple property. I want to use this opportunity to learn about the code to contribute more in the future.

If you're keen to work on this, having a simple property in application-core.properties mapped to ApplicationProperties would be a start to getting your PR merged.
Everything else needs more thought from my side, unfortunately :)

Hi @fabapp2
I have raised a PR for the property. In the meantime, I am going through the code to understand it better and be ready for bigger contributions.

closed with #912


build: Add separate dev and prod builds and add source-maps to dev build 🎉

fixes #3328
Try here
TODOS

[ ] Update changelog
[ ] Release patch version

Would it work to just build source maps and let people not deploy them if they don't want?

Would it work to just build source maps and let people not deploy them if they don't want?

Earlier I had tried loading sourcemaps via cdn in https://github.com/excalidraw/excalidraw/pull/2825 but that doesn't work with web bundler since webpack doesn't understand from where to build the source maps for the umd build(same would apply for if host has to deploy the source maps to their cdn right ?).
So I have exposed the sourcemaps using eval-source-map for dev builds only.

Would it work to just build source maps and let people not deploy them if they don't want?

Earlier I had tried loading sourcemaps via cdn in #2825 but that doesn't work with web bundler since webpack doesn't understand from where to build the source maps for the umd build(same would apply for if host has to deploy the source maps to their cdn right ?).
So I have exposed the sourcemaps using eval-source-map for dev builds only.

I see. Ok.

So I digged into the sourcemaps again but didn't find an efficient way to expose source maps for production build.
The issue I think is coz its umd build so mapping to original source code is not happening as its one minified bundle when we try to host the source maps from external source (cdn), webpack/browser is not able to detect it, it works fine when using in browser directly(script tag).
I will try out the plugin source-map-loader in host to see it can help in fixing this and raise a separate PR if it works out.
If we expose the transpiled code then this wouldn't be an issue since webpack will be responsible to map it in host.(I will revisit this soon)
For dev build the source maps are inlined so of course this will increase the bundle size of dev build (~3.88 MiB) but since its just for dev build so we need not worry about that and it gives the best quality source maps with original code. But at least now host can debug in dev mode which wasn't possible earlier so I think we can merge this.


TestPurge fails on GHA macOS runner

We recently got very consistent test failure on GHA macOS runner for the TestPurge case: https://github.com/PelicanPlatform/pelican/actions/runs/8802684671/job/24159026949?pr=1146
It's very hard to make the test work, which usually requires re-running a bunch of times, so we should really fix the failure.

Make the TestPurge for linux only.


Added Support for Tuya Zemismart 3 Phase Power Meter _TZE200_v9hkz2yn variant

Proposed change
Added Support for Tuya Zemismart 3 Phase Power Meter
Additional information

[x] The changes are tested and work correctly
[x] pre-commit checks pass / the code has been formatted using Black
[ ] Tests have been added to verify that the new code works

@TheJulianJES  hi, I would like this PR to be reviewed and merged so that support for 3 phase power monitor can be added in ZHA. TIA

@TheJulianJES hi, I would like this PR to be reviewed and merged so that support for 3 phase power monitor can be added in ZHA. TIA

@TheJulianJES hi, I would like this PR to be reviewed and merged so that support for 3 phase power monitor can be added in ZHA. TIA

@TheJulianJES hi, I would like this PR to be reviewed and merged so that support for 3 phase power monitor can be added in ZHA. TIA

@dmulcahey @TheJulianJES Hi,
I would like this PR to be reviewed and merged so that support for 3 phase power monitor can be added in ZHA. I have personally tested this code locally and its working perfectly.
Thanks.

@dmulcahey @TheJulianJES Hi,
I wanted to ask if there is a time frame for the PR to be reviewed and merged? It would be great if the support for this device could be released soon.
Thanks.


When upgrading k8s in mixed clusters, windows nodes are left unavailable after upgrade finishes due to kubelet issues

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Upgrade K8s version via Rancher UI on a GCP mixed cluster:
v1.15.9-rancher1-1 upgrade to  v1.16.6-rancher1-2 (not specific to any starting k8s version)
linux cp/etcd master 1m25s
linux worker 4m15s
windows worker kubelet error ~6m
error: Kubelet stopped posting node status.
except the node reports a successful upgrade at the same time it shows an error in the UI:
time="2020-02-01T05:46:19Z" level=info msg="{\"status\":\"Status: Downloaded newer image for rancher/hyperkube:v1.16.6-rancher1\"}"
time="2020-02-01T05:46:24Z" level=info msg="For process kubelet, Image has changed from rancher/hyperkube:v1.15.9-rancher1 to rancher/hyperkube:v1.16.6-rancher1"

Result:
specific to GCP and mixed clusters, kubelet on windows nodes fail after a k8s upgrade and the nodes become unreachable / unscheduable
kube-proxy error
INFO: Waiting for servcie-sidekick to prepare the entrypoint.ps1 ...
Cannot index into a null array.
At C:\opt\rke-tools\entrypoint.ps1:202 char:13
+             $subnet = $hnsNetworkObj.Subnets[0].AddressCIDR
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : NullArray

kubelet errors
I0201 05:53:59.782009 6624 metadata.go:219] Failed to Get service accounts from gce metadata server: Get http://metadata.google.internal./computeMetadata/v1/instance/service-accounts/: dial tcp: lookup metadata.google.internal.: getaddrinfow: The requested name is valid, but no data of the requested type was found.
and
E0205 19:17:24.653032    6512 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
        For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Other details that may be helpful:
this is not specific to any k8s version.
windows versions used on GCP:
windows-server-1909-dc-core-for-containers-v20200114
windows-server-1909-dc-core-v20200114 (installed Docker myself, same result)
same upgrade process in AWS succeeds with no kubelet errors:
AWS mixed cluster:
v1.15.9-rancher1-1 upgrade to v1.16.6-rancher1-2
cp/etcd master node  ~1minute
linux worker rancherOS  ~3 minutes
linux worker ubuntu ~4 minutes
windows worker node ~5 minutes
same windows node upgrade message
time="2020-02-01T04:57:52Z" level=info msg="For process kubelet, Image has changed from rancher/hyperkube:v1.15.9-rancher1 to rancher/hyperkube:v1.16.6-rancher1"
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.3.3

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): cloud - gce large and xlarge
Kubernetes version (use kubectl version):v1.15.9
Docker version (use docker version): 19.03.5

@rosskirkpat , the cause is that the querying metadata route might be dropped after flannel started. We can divide into two scenarios to discuss:

Without GCE cloud provider:
After starting, we can repair the losing metadata manually in the following ways:

login into Windows nodes
open powershell
cd c:\etc\rancher\wins
exec .\wins.exe cli route add --addresses "<IP_ADDRESS>"

With GCE cloud provider:
Rke-tool will repair the losing route before starting kubelet/kube-proxy with https://github.com/rancher/rke-tools/blob/64c1facb4b6e5685f9ec70d0bf8074035d8acc3e/windows/sidecar.ps1#L77-L78

I personally think there are two problems here:

Without the cloud provider setting, kubelet should treat all running hosts equally, but how could it know the platform is GCE and why it needs to query metadata server?
The Windows host on GCE is very strange, it will not rebuild the querying metadata route after the network interface is refreshed, but AWS and Azure will do that.

FYI:

Flannel only builds the HNSNetwork and manages those HNSEndpoints/HNSPolicies below the built HNSNetwork.
GCE cloud provider setting could follow https://gist.github.com/thxCode/3d6805a904fdb34a03010c0908e25bed

Confirmed with Support no further action is required from engineering side.


Use webhook to deploy to servers

Instead of letting GitHub Actions to connect to SSH, we can set up webhooks (ex. https://github.com/adnanh/webhook) which will run a script to pull Docker images and run services.

What's wrong with SSH script?

@evermake Microsoft knows too much about your server

What's wrong with SSH script?

It gives GitHub access to our servers. If something goes wrong (e.g. GitHub's security mechanisms allowed some modifications in workflows we use), our production servers may be compromised.


[SPARK-12177] [STREAMING] Update KafkaDStreams to new Kafka 0.9 Consumer API

…mer API

Can one of the admins verify this patch?


Projections cli not working as expected in Marten 6

Regardless of what command I'm running, e.g:
dotnet run -- projections -i --rebuild
dotnet run -- projections -i
dotnet run -- projections --list

It seems to immediately start running the projections. I would expect to go into interactive mode or being listed the different projections I have.
Output:
Building...
info: Marten.Events.Daemon.AsyncProjectionHostedService[0]
      Started HighWaterAgent
info: Marten.Events.Daemon.AsyncProjectionHostedService[0]
      Starting projection agent for 'Booking:All'
info: Marten.Events.Daemon.AsyncProjectionHostedService[0]
      Projection agent for 'Booking:All' has started from sequence 80 and a high water mark of 80

@nmowatt Hey, before we call this a bug, what's your Marten setup for the daemon like? And how are you applying Oakton?

Did you try to use the projections cli in Marten 6 @jeremydmiller ? E.g. projections --list

@nmowatt "I'm not using Oakton explicitly in any way, so not sure how that will be applied."
-- Oakton is what relays the command line options to the projections command.
See the docs here: https://martendb.io/configuration/cli.html
So at no point are you even executing the projections command. What you're seeing is the application just start up normally.


Feature/updated dropdown field

Description

Rewrote DropdownField from Class component to Functional component
Added 5 stories for Storybook (e.g default, multi lines, default value, no default items, with error)
Added Storybook addon, action. Logging dropdown field's on select action.

On what platform have you tested the change?

[x] Android - Emulator
[ ] Android - Physical device
[x] iOS - Emulator
[ ] iOS - Physical device

Screenshots
Please attach screenshots showing the change if relevant
Checklist

[ ] I have updated mockServer
[x] I have run npm test
[ ] I have run npm run test:i18n

Out of scope and potential follow-up
Is there any related changes that you plan to do in a follow-up PR or voluntarily excluded from the scope?

Cheers @selvach. I can't take much credit, most work is defo from Massimo.
Almost all changes have been added. with [4] it is not a self closing element. (Is that why you wanted to remove the line?)

Sorry - my comment for [4] was to just extract out the inline style into the stylesheet below. Just a minor suggestion for consistency - please ignore if you prefer!

@selvach Ah. I just misunderstood, thats all.

One last comment - can you take a look at the color of the icon? :)
The design uses #565A5C which is the primary color in the colors module, compared to the bluish color that is used.

@abubuwe Good spot!


migration fails when switching from crest to develop branch

See #162 discussion for background. I don't know if it broke because of the branch switch or because there is something wrong with the migration code. If it's the former I guess it doesn't matter really.
Error during the migration is:
  Applying djcelery.0001_initial...Traceback (most recent call last):
  File "./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    utility.execute()
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 346, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/core/management/base.py", line 394, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/core/management/base.py", line 445, in execute
    output = self.handle(*args, **options)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 222, in handle
    executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/migrations/executor.py", line 110, in migrate
    self.apply_migration(states[migration], migration, fake=fake, fake_initial=fake_initial)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/migrations/executor.py", line 148, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/migrations/migration.py", line 115, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/migrations/operations/models.py", line 59, in database_forwards
    schema_editor.create_model(model)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/base/schema.py", line 286, in create_model
    self.execute(sql, params or None)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/base/schema.py", line 111, in execute
    cursor.execute(sql, params)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/utils.py", line 98, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 62, in execute
    return self.cursor.execute(sql)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 124, in execute
    return self.cursor.execute(query, args)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/MySQLdb/cursors.py", line 205, in execute
    self.errorhandler(self, exc, value)
  File "/home/maptool/eve-wspace/local/lib/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
django.db.utils.OperationalError: (1050, "Table 'djcelery_crontabschedule' already exists")

The migrations worked fine updating my Ubuntu 16.04 install that had only had the develop branch. So I think this is purely an issue switching when from crest to develop

Since you already have a djcelery_crontabschedule table you apply that specific migration with the --fake option behind it.
`python manage.py migrate djcelery 0001 --fake
Should do the trick.

Ah I didn't know you could do that, TIL. :bulb:
Well it's not a big deal as the Ubuntu 16.04 EC2 instance works fine with the updated requirements.txt, I can just trash this instance.


fix(utils): exclude empty files

Proposed Changes

exclude empty files from being possibleDocker
add unit test

I submit this contribution under the Apache-2.0 license.

The master version already has this fixed, with the same results as this branch.


Fix build for FreeBSD

Hi folks,
first of all thank you for this very useful library. It makes realizing my current project much easier and more convenient. This PR adds support for FreeBSD as target_os is missing. I tested the build for FreeBSD 13.0-CURRENT and 12.1-RELEASE.
Thank you very much!
Best Regards

This is now in the master branch and Rutie crate 0.8.2


only us keyboard layout

In there any way to change the keyboard layout instead of typing a q to get an a on azerty because that is really annoying

If you build it yourself I will say kind "yes" but if you use a prebuild like the CJMCU-3212 board no...
Use this repo:
https://github.com/spacehuhn/WiFiDuck
Be careful you will need to rewire the ESP8266 to the ATmega32u4. It's the reason you can't change the layout on a CJMCU-3212 without modifying the code.

You can also edit the keyboard.h file found in Arduino folder: ...\Arduino\libraries\Keyboard\src\Keyboard.cpp


Test verify, merge and release jobs

/release 1.0.12

/release 1.0.13

/release 1.0.14

/release 1.0.15

/release 1.0.16


As a ramen developer/tester, I can issue a ramen end-to-end automated test on a Linux instance with podman and without docker so that ramen can be tested

Issue reported by @ShyamsundarR in https://github.com/RamenDR/ramen/pull/60#discussion_r653886962, encountered on Fedora but not RHEL7 or Ubuntu instances.
ocm-minikube-ramen.sh podman differences from docker:

docker installation skip; existing podman use instead
ramen image load to minikube clusters method varies
DOCKER_HOST variable not needed
ramen image build command varies? or is docker an alias for podman?

I intend to complete this for sprint 2 ending 2021-July-2.

Issue addressed in pull request https://github.com/RamenDR/ramen/pull/60


Spatial Understanding Shape HalfDims always returns (0,0,0)

Overview
When using SpatialUnderstandingDllShapes.QueryShape_FindPositionsOnShape(...) and querying halfDims they always return (0,0,0).
Expected Behavior
halfDims returns correct dimensions
Actual Behavior
halfDims returns (0,0,0)
Steps to reproduce
Using my SpatialUnderstanding tutorial here and trying to access shapeResult[0].halfDims inside the InstantiateObjectOnTable() func always returns (0,0,0)
Unity Editor Version
2017.4.3f
Mixed Reality Toolkit Release Version
2<IP_ADDRESS>

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


Feature/installation instructions

Steps to help our newest users:

Created shell scripts to run Dismod-AT on the cluster or from Docker
Documented dmcsv2db script, the one that mimics Brad's script
Documented installation of Cascade
Made a Pip requirements.txt file that includes the IHME db-queries requirement.

The last one is because there isn't a good way to install our software with the IHME install_extras.
The review I want is twofold.

Is making the shell scripts to run Dismod-AT a good idea?
Does Cascade installation and running of Dismod-AT with those scripts work for you?

We now have four separate versions of our dependency list? This can't possibly be necessary.


Skipforward and skipforward issue

I'm little confused can any one help me how to skip forward 30 sec and skip backword 30 sec on clicking button (IbAction)

get the current from your player obj ie -

var seekTime = player.currentTime

then add + 30 for forward and -30 for backward

get the current from your player obj ie -

var seekTime = player.currentTime

then add + 30 for forward and -30 for backward

Hi since currentTime is get property only where I add +30 or - 30 sec

if i would have understood correctly , store the current time + 30 and add the update value on
for example if u want to do forward
var seekTime = player.currentTime + 30
player.seek(to: Double(seekTime))

this will forward your audio

nop unfortunately its not working

can u share your code if possible


⚠ Bofrost.de has degraded performance

In d165413, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1887 ms

Resolved: Bofrost.de performance has improved in 7fcf1a8 after 6 minutes.


Boost wormholes usage to one/second by ignoring cooldowns.

You can use wormhole each tick if a NL was applied during the last second, which is always the case in WHs rooms. You don't have to wait for the cooldown to be updated.

Oh, I see that it is already included in #272 pull request. Just the hasItem check is missing from there. So I am closing this request.


WIP: create-react-app#675 webpack aliases from env variable

Allow webpack aliases to be defined in an env variable to prevent duplicate React issue (create-react-app#675)
https://github.com/facebookincubator/create-react-app/issues/675#issuecomment-348545153

Sorry, I'm pretty sure we won't be going this route. This is essentially adding configuration, but in a very ad-hoc way. So it's actually worse than having a proper configurable solution like webpack.

Makes sense


[BUG]: ansible run in CI is broken

Bug Report
At the moment the ansible-setup test in the ci-pipeline failes for an unknown reason. The ansible scripts were not modified. Also a new execution of the pipeline hours later doesn't fixed the problem. Maybe a problem with a pip-package, because maybe they are not pinned.
Error-Message: Error connecting: Error while fetching server API version: Not supported URL scheme http+docker
Maybe branch v0.4.x is also affected.

Current Behavior:

pipeline failes

Expected Behavior:

pipeline success

Steps To Reproduce:

run ci-pipeline on develop-branch

Environment:

current develop-branch in ci-pipeline

Anything else:

https://github.com/kitsudaiki/Hanami/actions/runs/9161729871

see issue: https://github.com/docker/docker-py/issues/3256

Fixed problem by pinning the requests package to version 2.31.0. This is only a workaround and has to be removed again in the future. To keep track of this a new issue was created: https://github.com/kitsudaiki/Hanami/issues/330


Do not autoPan if hover

closes https://github.com/boundlessgeo/qgis-webappbuilder-plugin/issues/372

Coverage remained the same at 73.513% when pulling 08b0be48387c53922001a207ac9ba3aa056d583c on autopan-hover into 173609c000185ee7cccd629d544c784ef963f543 on master.


Documentation on loading different versions of a CryptoKeyVersion

Hello,
We are trying to perform operations using different versions of the keys to support older clients.
What is the syntax to use the older versions of the keys?
openssl req -new -x509 -days 3650 -subj '/CN=test/' -sha256 -engine pkcs11   -keyform engine -key pkcs11:object=keyName > my-request.crt
Seems to always use the latest one?

Hello,
Correct, using pkcs11:object along with the CryptoKey name defaults to the latest version. The IDs set by our library, which can be used with pkcs11:id, correspond to the full KMS resource name (eg. projects/some_project/locations/some_location/keyRings/some_keyring/cryptoKeys/some_CK/cryptoKeyVersions/1).
You should be able to use
openssl req -new -x509 -days 3650 -subj '/CN=test/' -sha256 -engine pkcs11   -keyform engine -key pkcs11:id=projects/...../cryptoKeyVersions/X;type=private > my-request.crt

where X is the right version number.
Note that, when invoking pkcs11-tool with -O to list the objects, the key IDs are automatically hex-encoded by the tool and may seem different at first.

Ahh, thanks so much! I couldn't find any documentation on the ID field in the website!

Can we please update the user-guide and KMS documentation to include reference to this? There are no currently available docs highlighting the ability to call on the cryptoKeyVersion by id.

Yeah that's a very reasonable ask - will do.

Thank you @bdhess, much appreciated.

This is now part of both the user guide and the cloud.google.com reference docs.


Sympy not embedding inline

Description of your problem
When trying to display sympy modules in the IPython console, it simply displays the repr, rather than embedding it:
What steps will reproduce the problem?

from sympy import * (which spyder claims to already have done but doesn't work)
Integral(symbols("x"))

What is the expected output? What do you see instead?

The regular IPython console (Terminal: Termite) does display it in unicode, but still not in the rendered LaTeX:

I'm guessing this is partially related to the IPython console claiming it instantiated variables (matplotlib, numpy, sympy) but I can't access any variables they claimed to have displayed. I cannot re-run init_session as it has already been called by Spyder.
Please provide any additional information below
Versions and main components

Spyder Version: 3.2.6
Python Version: 3.6.4
Qt Version: 5.10.0
PyQt Version: 5.10
Operating system: Arch Linux x64

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
IPython >=4.0    :  6.2.1 (OK)
cython >=0.21    :  None (NOK)
jedi >=0.9.0     :  0.11.1 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.14.0 (OK)
pandas >=0.13.1  :  None (NOK)
psutil >=0.3     :  5.4.3 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.8.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
sphinx >=0.6.6   :  1.6.6 (OK)
sympy >=0.7.3    :  1.1.1 (OK)

Before trying to get the output of Integral(symbols("x")), you need to run
from sympy import init_printing()
init_printing()

I cannot re-run init_session as it has already been called by Spyder.

I forgot to mention you need to do that because _init_session is broken in the latest Spyder releases.

What sympy version is recommended?

I think 1.0 is working fine


CRN-804 - Normalise url and title to support identification of duplicates

I'd be tempted to use a generic type on the normalise function so that the input type and return type are guaranteed to match.

I'd be tempted to use a generic type on the normalise function so that the input type and return type are guaranteed to match.

I agree


Do not fail saving all drives if some of them are incorrect.

If there are multiple drives to save then all if any of them is incorrect then the whole update fails.
AC:

correct drives are saved always (even if there are also incorrect drives in the same batch)
incorrect drives are marked as reddish when backend fails to save them

@adamgajzlerowicz


About the SAD in ENet-label-torch

After studying the paper and the model, I have several questions about the SAD and the training process:

As mentioned in the paper that SAD is added in the 40K episodes. Does this mean that the training process need to have two stages, first is use the model without SAD and the second use the model with SAD?
from the model definition, seems that there are only 2 attention maps added, not as shown as in Fig.3 in the paper, do I understand right?
I am still confusing on how the attention maps improves the result. Just as shown in Fig.3 in the paper, seems that the attention maps not contribute on the final result. Meanwhile, as in the code, just concatenate the attention map with the output from stage 2 and 4(if I understand right) seems also not affect the original data flow. Please help me on clarifying this.

Thanks!

Yes.
Yes. As to other mimicking path, you need to add it by yourself.
SAD improves the representation learning of the model and hence it improves the prediction. The code in ENet-Label-Torch contains the process of block 3 mimicking block 4 and block 4 mimicking the label.

Hi,
Thanks for your reply.
As for the third question, does block 4 means the decoder block? Seems from the model definition, the block 3 and block 4 are combined with one attention map?
Another question is the last attention map is the one as you mention that is the block 4 mimicking the label?

@cardwing I have a similar question. I have no experience with Lua, but I have experience with PyTorch and other frameworks. I don't see "block 3 mimicking block 4" in the code. If I understood correctly, and maybe I didn't, this code:
https://github.com/cardwing/Codes-for-Lane-Detection/blob/a224eb4d38cf3294ea80b2d4181f8afe028d801e/ENet-Label-Torch/train.lua#L71-L80
seems to be applying:

Spatial CE between 1st output and target[1]
Binary CE between 2nd output and target[2]
MSE between 3rd output and target[1]
MSE between 4th output and target[1]

as defined in:
https://github.com/cardwing/Codes-for-Lane-Detection/blob/a224eb4d38cf3294ea80b2d4181f8afe028d801e/ENet-Label-Torch/models/init.lua#L158-L162
Because of my lack of experience with Lua, I don't know where to find in the code what target is, but based on the loss definition, target[1] is the segmentation map and target[2] is the existence ground-truth. In that case, it seems to me that both SAD modules are trying to mimic the label. Is that correct?
I am trying to plug SAD modules to ENet-TuSimple-Torch to retrain and get the model with 96.64%, but it seems I won't have it done before my deadline and I won't be able to include your method in the comparison :(

That's true. I leverage deep supervision to finetune the performance of ENet-SAD and that's why the F1-measure of the provided code is better than the reported F1-measure on CULane (72.0 v.s. 70.8). As to TuSimple, since many baselines have so strong performance, several engineering tricks (e.g., warm up pre-training, lane smoothing and lane postprocessing) have been utilized to make ENet-SAD have comparable performance. You can have a test of the ENet model on TuSimple. It can achieve better result (Accuracy: 0.9486756915, FP: 0.0457901133, FN: 0.0386712197) than the reported performance (0.9302 accuracy). Reproducing the performance of ENet-SAD on TuSimple is a bit difficult since several engineering tricks are not included in the current code. If you have limited time and resources, you may just include the performance of ENet which is an essential backbone of our method.

Could you give us more details on what kinds of "engineering tricks" were used?

Like utilize image cropping to remove areas without lanes, use a smaller learning rate to pretrain the model, replace the conventional convolution with dilated convolution, cut the predicted lanes shorter if they are too long, smooth the predictions if necessary, etc.

@cardwing I have a similar question. I have no experience with Lua, but I have experience with PyTorch and other frameworks. I don't see "block 3 mimicking block 4" in the code. If I understood correctly, and maybe I didn't, this code:
https://github.com/cardwing/Codes-for-Lane-Detection/blob/a224eb4d38cf3294ea80b2d4181f8afe028d801e/ENet-Label-Torch/train.lua#L71-L80
seems to be applying:

Spatial CE between 1st output and target[1]
Binary CE between 2nd output and target[2]
MSE between 3rd output and target[1]
MSE between 4th output and target[1]

as defined in:
https://github.com/cardwing/Codes-for-Lane-Detection/blob/a224eb4d38cf3294ea80b2d4181f8afe028d801e/ENet-Label-Torch/models/init.lua#L158-L162
Because of my lack of experience with Lua, I don't know where to find in the code what target is, but based on the loss definition, target[1] is the segmentation map and target[2] is the existence ground-truth. In that case, it seems to me that both SAD modules are trying to mimic the label. Is that correct?
I am trying to plug SAD modules to ENet-TuSimple-Torch to retrain and get the model with 96.64%, but it seems I won't have it done before my deadline and I won't be able to include your method in the comparison :(

Hi! I am working on implementing the SAD in Pytorch for CULane. We have similar questions to how the SAD works. This question specifically:
Because of my lack of experience with Lua, I don't know where to find in the code what `target` is, but based on the loss definition, `target[1]` is the segmentation map and `target[2]` is the existence ground-truth. **In that case, it seems to me that both SAD modules are trying to mimic the label.** Is that correct?
Have you by any chance figured out how this works?

You can just replace the target label with the output of block 3 and block 4. You can also add deep supervision to the output of block 4 to further boost the performance.


_7zz: replace fetchurl with fetchzip for stabler hashes

Description of changes
See https://github.com/NixOS/nixpkgs/pull/322145#issuecomment-2205983022:

No, the version is the same. The archives contain the same files and metadata according to diffoscope but the archive itself is different.
Perhaps we should be using fetchunzip instead of re-packing, since the flags we pass to tar are clearly not sufficient to ensure deterministic output across versions. (If the source modification actually necessary.)

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Apparently nixpkgs-review doesn't work here
       > warning: collision between `/nix/store/985d8hfiw5h48i0dihh4p57kdbhaxbib-pixelfed-0.12.1/webpack.mix.js' and `/nix/store/2y2jxbqcvp1zdpxm2k6x1iss0bw422gq-librenms-23.9.1/webpack.mix.js'
       > warning: collision between dangling symlink `/nix/store/985d8hfiw5h48i0dihh4p57kdbhaxbib-pixelfed-0.12.1/.env' and dangling symlink `/nix/store/zbz9gzirmi6f9bz5aidmw80l8mj11f0a-bookstack/.env'
       > warning: collision between dangling symlink `/nix/store/985d8hfiw5h48i0dihh4p57kdbhaxbib-pixelfed-0.12.1/storage' and dangling symlink `/nix/store/zbz9gzirmi6f9bz5aidmw80l8mj11f0a-bookstack/storage'
       > error: not a directory: `/nix/store/985d8hfiw5h48i0dihh4p57kdbhaxbib-pixelfed-0.12.1/bootstrap'
       For full logs, run 'nix log /nix/store/cyb4rs2svqk361461qbh0s8xhc09ix7z-env.drv'.

Thanks.  I'm sorry for the UI blowup.  It's just a single commit.  Suboptimal order of my actions.


fix: Middleware will now also get invoked for health and admin API

Codecov Report

Merging #345 (8a6f5f5) into main (9a921de) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #345      +/-   ##
==========================================
- Coverage   29.23%   29.20%   -0.03%
==========================================
  Files          61       61
  Lines        6520     6526       +6
==========================================
  Hits         1906     1906
- Misses       4396     4402       +6
  Partials      218      218

Impacted Files
Coverage Δ

server/services/v1/admin.go
0.00% <0.00%> (ø)

server/services/v1/health.go
0.00% <0.00%> (ø)

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 9a921de...8a6f5f5. Read the comment docs.


#16 Add new blacklist mode for CookieActivator

Coverage remained the same at 100.0% when pulling 918792311d0abfcb9329bf1d6eaedcbf36418f73 on feature/16-blacklist-mode into fad815f3905134cd47fd6ee45ca714f2bf82b0de on master.


How to draw fiducials in 2D image?

Hello,
when I try to use img and pred_img to draw projected landmarks in register.py, I find that the landmarks and img are not in the same scale. The specific code and the observed result are as follows:
pred_img, mask = registration()
loss = self.criterion(pred_img, img)
losses.append(loss.item())
times.append(0)
est_pose = registration.get_current_pose()
true_fiducials_2d, pred_fiducials_2d = self.specimen.get_2d_fiducials(idx, est_pose)
Create a new figure and subplots
fig, axs = plt.subplots(1, 2, figsize=(10, 5))  # Adjust figsize as needed
Display the original image
axs[0].imshow(img.squeeze().cpu().numpy(), cmap='gray')
axs[0].axis('off')  # Hide axes
axs[0].set_title('Original Image')
axs[0].scatter(
pred_fiducials_2d[0, ..., 0].detach().numpy(),
pred_fiducials_2d[0, ..., 1].detach().numpy(),
marker="x",
c="tab:orange",
)
print("pred_img", pred_img)
Display the registered image
axs[1].imshow(pred_img.detach().cpu().numpy()[0,0], cmap='gray')
axs[1].axis('off')  # Hide axes
axs[1].set_title('Registered Image')
axs[1].scatter(
true_fiducials_2d[0, ..., 0].detach().numpy(),
true_fiducials_2d[0, ..., 1].detach().numpy(),
label="True Fiducials",
)
axs[1].scatter(
pred_fiducials_2d[0, ..., 0].detach().numpy(),
pred_fiducials_2d[0, ..., 1].detach().numpy(),
marker="x",
c="tab:orange",
label="Predicted Fiducials",
)
for idx in range(true_fiducials_2d.shape[1]):
axs[1].plot(
[true_fiducials_2d[..., idx, 0].item(), true_fiducials_2d[..., idx, 0].item()],
[true_fiducials_2d[..., idx, 1].item(), true_fiducials_2d[..., idx, 1].item()],
"w--",
)
I tried another approach, and here's the code. It resulted in an error.
true_xray , _ = self.specimen[idx]
pred_xray = self.drr(est_pose)
true_fiducials_2d, pred_fiducials_2d = self.specimen.get_2d_fiducials(idx, est_pose)

error:
File "/home/data/cyx/autodl-tmp/DiffPose-main/experiments/deepfluoro/register.py", line 224, in run
pred_xray = self.drr(est_pose)
^^^^^^^^^^^^^^^^^^
File "/home/data/cyx/miniconda3/envs/preop/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/data/cyx/miniconda3/envs/preop/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: DRR.forward() missing 2 required positional arguments: 'translation' and 'parameterization'
Can you help me identify the reason?

Hi @CYXYZ , the reason for this is because I've updated DiffDRR after releasing DiffPose.
I think if you install pip install diffdrr==0.3.8, all the code in the DiffPose repository will work.
Alternatively, I am updating all the code in DiffPose to work with the latest version of DiffDRR (the update lives in the branch refactor-se3). I'm aiming to release this before the camera ready deadline for CVPR. You can also try using the code in this branch - I'm 90% confident everything works as intended, still need to test a few more functions.

The scale of x-ray ranges from 0 to 256, while the scale of fiducials is 1436.

Hi @CYXYZ , no problem at all, I'm more than happy to help! Makes me glad to see that the tool is useful for other people.
So when we downsample the image from 1436 pixels -> 256 pixels, we need to adjust the pixel spacings appropriately.
The subsampling factor is subsample  = (1536 - 100) / 256. So dividing your 2D fiducial markers by subsample should rescale them to [0, 256].

Dear vivek,
I wanted to express my gratitude for your guidance and assistance in addressing the challenges I encountered recently.    Thanks to your valuable advice, I was able to overcome the obstacles I faced.
I have been closely studying your articles and have found them to be incredibly insightful.    I am eager to build upon the knowledge and insights you have shared and to contribute to further advancements in our field.
I am currently working on implementing some improvements based on the methods discussed in your articles.    I am excited about the opportunity to innovate and refine existing methodologies.
Thank you once again for your support and mentorship.    I look forward to future opportunities to collaborate and exchange ideas.
Warm regards,
cyxyz

Great, glad to hear you solved your problem. Looking forward to reading what you do with this code!


Merge Kentik Branch Into Main

Look at merging the Kentik branch into the main section.

Cool, this is kinda just tieing all the loose ends together. I think ktranslate is going to halt development going forward so will be a good place to leave things.


Issue #56 - enable use of embedded Derby DB

Signed-off-by: Mike Schroeder<EMAIL_ADDRESS>

I ran into the same problems running helm-docs in Windows, so I manually removed the blank line and trailing whitespace. Not sure why it happens tbh.


Make editing description consistent with everything else

The "description" field edits don't work like anything else, and that inconsistency is jarring. It should support left-click to edit, alt+left click to select like everything else. UIs are more complicated when there are inconsistencies.

Editing description is consistent now (https://github.com/expln/metamath-lamp/issues/97)


IMDB example import error

My Environment

ArangoDB Version:        3.4.1
Storage Engine:             default
Operating System:        Win 10 pro latest build
Total RAM in your machine:        32Gb
Disks in use:        SSD

When trying to import IMDB I follow these steps in command prompt:
CD into the Graphs\IMDB folder
arangosh
require("internal").load("import.js")
I get 2 errors.
error 1:
Even if IMDB graph does not exist, I get an error that it does. It was created, So I delete. I re-run, I get the error again.
Temp Solution:
Remove from import.js:
try {
    g = gm._create(gName);
    g.drop();
  } catch (e) {

  }

error 2:
running require("internal").load("import.js") again I get:
JavaScript exception in file 'import.js' at 32,7: TypeError: g.addVertex is not a function
!    g.addVertex(d._key, d);
!      ^
stacktrace: TypeError: g.addVertex is not a function
    at Function.storeVertex (import.js:32:7)
    at import.js:61:12
    at import.js:63:2
    at <shell command>:1:21

Please help! I'm hoping not to use Linux, bash or WSL for this project. Thanks!

Any ideas on tis one?

https://github.com/arangodb/example-datasets/issues/7 related.

https://github.com/arangodb/example-datasets/commit/ece77c9b056bd26c44ce0205b872256485ae0752 fixed the example.
Please note ArangoDB 3.7 is available.


CVE issues in go stdlib of mkcert

Environment

Ubuntu 22.04
1.4.4

What you did
RUN sudo -E wget https://github.com/FiloSottile/mkcert/releases/download/v1.4.4/mkcert-v1.4.4-linux-amd64
&& sudo -E mv mkcert-v1.4.4-linux-amd64 mkcert
&& sudo -E chmod +x mkcert
&& sudo -E cp mkcert /usr/local/bin/
What went wrong
Seems this binary uses Go stdlib 1.18, and that has a number of CVEs that are fixed in 1.19.8:

CVE-2023-24538
CVE-2023-29402
CVE-2023-24540

and a couple more

Same issue. Any updates on this?

None of those affect mkcert. mkcert doesn't even use those packages.

Yes, but if you're using that version of the stdlib, the automated tools that highlight container vulnerabilities will fire because of mkcert. It would be very helpful if you updated the tool to avoid this issue.

I don't think using automated tools that fail to do even package-level scoping and then pushing the churn onto every upstream project to reduce noise is sustainable.
My responsibility is making sure mkcert is not affected by security vulnerabilities. The responsibility of your tools is making sure they don't disturb you with false positives.

Because what could possibly go wrong with a tool intended to manipulate the core trust infrastructure of a system that doesn't bother to use up to date libraries?

There is real risk in updating, too, and an updates policy is a more nuanced topic than "bothering to use up to date libraries". I assure you I am very aware of every vulnerability in the Go project.
Also, https://filippo.io/maintenance#conduct

I'm not arguing that you "owe it to people" or that it's trivial to do, but I think closing the issue with no discussion and saying the tools in wide use in the largest cloud providers in the world are "not sustainable" asserts a position in the ecosystem that is a bit detached from reality. Even the noise created by these detected vulnerabilities has an effect on the overall security of people using it, as it can reduce the contrast for real issues. I think it's loud and clear that it is not your concern, and for us certainly we will just move on to other options. I appreciate the effort that made the original tool.

Even the noise created by these detected vulnerabilities has an effect on the overall security of people using it, as it can reduce the contrast for real issues.

I agree. I just think the issue is best fixed in 5-10 tools, rather than in 50-100k projects.

That seems like a very hard problem to try and diagnose whether, at runtime, a particular binary touches a particular part of the code. I'm not super familiar with go packaging, but I can see how that could generate a lot of false negatives.


Incorporate monitoring objects.

Something like:
RE(my_scan, monitor=[det1, det2, ...])

and/or:
RE.monitor = [det1, det2]

which would apply to every scan.
This would create a separate Event stream for each detector, allowing asynchronous reads to be emitted/stored. It would force a read at the beginning of the scan. We still have to decide when these Events would be processed. (As discussed offline, since we can't control the rate of Event generation, we need some way of ensuring that a fast-changing monitored detector can't paralyze the scan.)

This is more or less addressed by the new ScanBase.flyers attribute, but I'll leave the issue open until we see it in use at the beamlines.

It works at CSX.


Enable RStudio launches

This PR enables RStudio launches from renku.

creates a renku-enabled rstudio image that is compatible with jupyter (based on the  nbrsessionproxy Dockerfile)
adds the ability to specify default_url as a query parameter. If the POST request includes ?default_url=/rstudio in the request url, RStudio is launched automatically. This should be included in the UI as part of https://github.com/SwissDataScienceCenter/renku-ui/issues/308.

closes #57

this is up on staging -- tested with curl to use default_url=rstudio and ended up spawning directly into the RStudio session as expected.

It looks mixed with the other pr. Do we merge the other one first?

it's been merged, I rebased this one on top

Ugh, github doesn't show the diff against master for some reason

yeah I had this problem yesterday with @jirikuncar's PRs that were layered on top of one another.