[0.9.3-rc2] fatal error: runtime: out of memory

I've been experimenting with InfluxDB, trying to measure stability and performance.
I wrote a test program (node.js script) that simulates inserting points in batch sizes of 8,000 - 20,000 points every 5 seconds.  I'm using the HTTP API (line protocol).  Each measurement is inserted with 5 tags, 1 field, and a timestamp.  Each tag has 10 possible values.
The InfluxDB database has 3 measurements:

esf_events -> receives the incoming data, retention policy of 3 days

esf_totals_5m -> continuous query runs every 5 minutes to create 5 minute summaries, retention policy of 10 days.

esf_totals_1h -> continuous query runs every hour to create 1 hour summaries, retention policy of 30 days.

InfluxDB is running in a Linux Virtual Machine -> Ubuntu 13.04 (GNU/Linux 3.8.0-30-generic x86_64).  The VM is configured with 3G of ram and 4 virtual CPUs.
Prior to the 9.3 builds, the test program would run for a few minutes and then Influx would return 500 errors.
Using the 9.3_rc2 build, the test ran for a few hours and then 500 errors started.  A quick review of the log file indicated compaction was taking a long time (over 14 seconds).  I stopped the test program and let influx sit idle.  After an hour+ (lunch break), I restarted the test program and immediately saw 500 errors.  Influx then died with an out of memory error.  Below is the log file snippet.
One additional observation:  While the test script is running (inserting points every 5 seconds), I use Grafana to graph the data.  As I manually refresh the graph, I watch the server load using top.  I've noticed the load in the 9.3 builds is significantly higher when executing the Grafana queries.  In the 9.0 - 9.2 builds, the load is about 40% when executing the queries.  In the 9.3 builds, the load is often maxed at 400% when executing the same queries.  When only inserting data (no queries), the load ranges from 5%-20%.
I can provide the node.js test script if desired.
Log File Snippet:
[http] 2015/08/24 11:38:31 <IP_ADDRESS> - - [24/Aug/2015:11:38:30 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - ef7f25c4-4a86-11e5-8300-000000000000 767.286045ms
[wal] 2015/08/24 11:38:32 Flush due to memory. Compacting 351 series from partition 1
[continuous_querier] 2015/08/24 11:38:32 executing continuous query totals_5m
[http] 2015/08/24 11:38:36 <IP_ADDRESS> - - [24/Aug/2015:11:38:36 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - f29186a4-4a86-11e5-8301-000000000000 563.007492ms
[wal] 2015/08/24 11:38:46 compaction of partition 1 took 14.630458939s
[wal] 2015/08/24 11:38:47 Flush due to memory. Compacting 333 series from partition 2
[http] 2015/08/24 11:38:47 <IP_ADDRESS> - - [24/Aug/2015:11:38:41 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - f5ff6149-4a86-11e5-8302-000000000000 6.192648581s
[http] 2015/08/24 11:38:50 <IP_ADDRESS> - - [24/Aug/2015:11:38:46 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - f8b616a4-4a86-11e5-8303-000000000000 4.092872824s
[wal] 2015/08/24 11:39:02 compaction of partition 2 took 15.767603983s
[continuous_querier] 2015/08/24 11:40:01 wrote 648 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/24 11:41:20 wrote 648 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/24 11:42:41 wrote 648 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/24 11:42:41 executing continuous query totals_1h
[continuous_querier] 2015/08/24 11:42:42 wrote 648 point(s) to esf.rp_30d.totals_1h
[continuous_querier] 2015/08/24 11:42:43 executing continuous query totals_5m
[retention] 2015/08/24 11:43:22 retention policy shard deletion check commencing
[retention] 2015/08/24 11:43:22 retention policy enforcement check commencing
[wal] 2015/08/24 11:43:48 Flush due to idle. Compacting 31221 series from partition 4
[continuous_querier] 2015/08/24 11:44:17 wrote 648 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/24 11:44:20 wrote 648 point(s) to esf.rp_10d.totals_5m
[wal] 2015/08/24 11:44:26 compaction of partition 4 took 38.585737288s
[wal] 2015/08/24 11:44:26 Flush due to idle. Compacting 31433 series from partition 5
[continuous_querier] 2015/08/24 11:44:43 executing continuous query totals_5m
[wal] 2015/08/24 11:47:44 Flush due to idle. Compacting 140 series from partition 1
[wal] 2015/08/24 11:47:50 compaction of partition 1 took 4.940487757s
[wal] 2015/08/24 11:47:50 Flush due to idle. Compacting 114 series from partition 2
[wal] 2015/08/24 11:47:51 compaction of partition 2 took 1.282193921s
[wal] 2015/08/24 11:47:51 Flush due to idle. Compacting 130 series from partition 3
[wal] 2015/08/24 11:47:52 compaction of partition 3 took 404.160209ms
[wal] 2015/08/24 11:47:52 Flush due to idle. Compacting 137 series from partition 4
[wal] 2015/08/24 11:47:53 compaction of partition 4 took 1.059641097s
[wal] 2015/08/24 11:47:53 Flush due to idle. Compacting 127 series from partition 5
[wal] 2015/08/24 11:47:53 compaction of partition 5 took 437.244976ms
[wal] 2015/08/24 11:49:22 Flush due to idle. Compacting 168 series from partition 2
[wal] 2015/08/24 11:49:25 compaction of partition 2 took 3.703569577s
[wal] 2015/08/24 11:49:25 Flush due to idle. Compacting 124 series from partition 3
[wal] 2015/08/24 11:49:25 compaction of partition 3 took 589.510992ms
[wal] 2015/08/24 11:49:25 Flush due to idle. Compacting 140 series from partition 4
[wal] 2015/08/24 11:49:27 compaction of partition 4 took 1.34646599s
[wal] 2015/08/24 11:49:27 Flush due to idle. Compacting 114 series from partition 5
[wal] 2015/08/24 11:49:27 compaction of partition 5 took 321.527385ms
[wal] 2015/08/24 11:49:27 Flush due to idle. Compacting 102 series from partition 1
[wal] 2015/08/24 11:49:27 compaction of partition 1 took 174.133819ms
[retention] 2015/08/24 11:53:22 retention policy enforcement check commencing
[retention] 2015/08/24 11:53:22 retention policy shard deletion check commencing
[continuous_querier] 2015/08/24 11:58:50 wrote 648 point(s) to esf.rp_10d.totals_5m
[retention] 2015/08/24 12:03:26 retention policy enforcement check commencing
[retention] 2015/08/24 12:03:26 retention policy shard deletion check commencing
[wal] 2015/08/24 12:03:50 Flush due to idle. Compacting 102 series from partition 1
[wal] 2015/08/24 12:03:58 compaction of partition 1 took 6.361118624s
[wal] 2015/08/24 12:03:58 Flush due to idle. Compacting 168 series from partition 2
[wal] 2015/08/24 12:04:06 compaction of partition 2 took 8.001159993s
[wal] 2015/08/24 12:04:06 Flush due to idle. Compacting 124 series from partition 3
[wal] 2015/08/24 12:04:08 compaction of partition 3 took 1.676805947s
[wal] 2015/08/24 12:04:08 Flush due to idle. Compacting 140 series from partition 4
[wal] 2015/08/24 12:04:09 compaction of partition 4 took 1.376699333s
[wal] 2015/08/24 12:04:09 Flush due to idle. Compacting 114 series from partition 5
[wal] 2015/08/24 12:04:10 compaction of partition 5 took 588.560226ms
[http] 2015/08/24 12:08:47 <IP_ADDRESS> - - [24/Aug/2015:12:08:34 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - 224d23d6-4a8b-11e5-8304-000000000000 12.181556728s
[http] 2015/08/24 12:08:47 <IP_ADDRESS> - - [24/Aug/2015:12:08:37 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - 241826e0-4a8b-11e5-8305-000000000000 9.780773933s
[http] 2015/08/24 12:08:49 <IP_ADDRESS> - - [24/Aug/2015:12:08:47 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 400 55 - - 2a5d349e-4a8b-11e5-8307-000000000000 1.976803057s
[http] 2015/08/24 12:08:52 <IP_ADDRESS> - - [24/Aug/2015:12:08:42 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - 2732b8ee-4a8b-11e5-8306-000000000000 10.43213712s
[http] 2015/08/24 12:09:10 <IP_ADDRESS> - - [24/Aug/2015:12:08:57 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - 300eabb7-4a8b-11e5-8308-000000000000 12.908354903s
[http] 2015/08/24 12:09:10 <IP_ADDRESS> - - [24/Aug/2015:12:09:07 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 400 55 - - 3650cb6e-4a8b-11e5-830a-000000000000 2.612207039s
[http] 2015/08/24 12:09:10 <IP_ADDRESS> - - [24/Aug/2015:12:09:02 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 500 8 - - 3335631b-4a8b-11e5-8309-000000000000 7.854739231s
[retention] 2015/08/24 12:13:47 retention policy enforcement check commencing
[retention] 2015/08/24 12:13:47 retention policy shard deletion check commencing
[continuous_querier] 2015/08/24 12:18:48 wrote 648 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/24 12:18:48 executing continuous query totals_1h
[continuous_querier] 2015/08/24 12:19:00 executing continuous query totals_5m
[wal] 2015/08/24 12:23:03 compaction of partition 5 took 38m35.994861759s
[wal] 2015/08/24 12:23:07 Flush due to idle. Compacting 31529 series from partition 1
[retention] 2015/08/24 12:23:22 retention policy enforcement check commencing
[retention] 2015/08/24 12:23:23 retention policy shard deletion check commencing
[wal] 2015/08/24 12:23:54 Flush due to idle. Compacting 124 series from partition 3
[wal] 2015/08/24 12:24:20 compaction of partition 3 took 24.421275024s
[wal] 2015/08/24 12:24:22 Flush due to idle. Compacting 140 series from partition 4
[wal] 2015/08/24 12:24:24 compaction of partition 4 took 2.01109078s
[wal] 2015/08/24 12:24:24 Flush due to idle. Compacting 114 series from partition 5
[wal] 2015/08/24 12:24:26 compaction of partition 5 took 2.197250952s
[wal] 2015/08/24 12:24:26 Flush due to idle. Compacting 102 series from partition 1
[wal] 2015/08/24 12:24:29 compaction of partition 1 took 2.757822998s
[wal] 2015/08/24 12:24:29 Flush due to idle. Compacting 168 series from partition 2
[wal] 2015/08/24 12:24:30 compaction of partition 2 took 1.603767268s
[retention] 2015/08/24 12:33:23 retention policy enforcement check commencing
[retention] 2015/08/24 12:33:24 retention policy shard deletion check commencing
[retention] 2015/08/24 12:43:22 retention policy enforcement check commencing
[retention] 2015/08/24 12:43:23 retention policy shard deletion check commencing
[metastore] 2015/08/24 13:28:56 Using data dir: /var/opt/influxdb/meta
[metastore] 2015/08/24 13:28:57 Skipping cluster join: already member of cluster: nodeId=1 raftEnabled=true peers=[localhost:8088]
[metastore] 2015/08/24 13:28:57 Node at localhost:8088 [Follower]
[store] 2015/08/24 13:28:57 Using data dir: /var/opt/influxdb/data
[wal] 2015/08/24 13:28:57 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/08/24 13:28:57 WAL writing to /var/opt/influxdb/wal/esf/rp_10d/2
[wal] 2015/08/24 13:28:57 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/08/24 13:28:57 WAL writing to /var/opt/influxdb/wal/esf/rp_30d/3
[metastore] 2015/08/24 13:28:58 Node at localhost:8088 [Leader]. peers=[localhost:8088]
[metastore] 2015/08/24 13:28:58 Updated node id=1 hostname=localhost:8088
[wal] 2015/08/24 13:29:01 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/08/24 13:29:01 WAL writing to /var/opt/influxdb/wal/esf/rp_3d/1
[handoff] 2015/08/24 13:29:08 Starting hinted handoff service
[handoff] 2015/08/24 13:29:08 Using data dir: /var/opt/influxdb/hh
[tcp] 2015/08/24 13:29:08 Starting cluster service
[shard-precreation] 2015/08/24 13:29:08 Starting precreation service with check interval of 10m0s, advance period of 30m0s
[snapshot] 2015/08/24 13:29:08 Starting snapshot service
[admin] 2015/08/24 13:29:08 Starting admin service
[admin] 2015/08/24 13:29:08 Listening on HTTP: [::]:8083
[continuous_querier] 2015/08/24 13:29:08 Starting continuous query service
[httpd] 2015/08/24 13:29:08 Starting HTTP service
[httpd] 2015/08/24 13:29:08 Authentication enabled: false
[httpd] 2015/08/24 13:29:08 Listening on HTTP: [::]:8086
[retention] 2015/08/24 13:29:08 Starting rentention policy enforcement service
2015/08/24 13:29:08 InfluxDB starting, version 0.9.3-rc2, branch 0.9.3, commit d0646a8871a583f8342afd0dc1a253946565d2cd
2015/08/24 13:29:08 GOMAXPROCS set to 4
[run] 2015/08/24 13:29:08 Listening for signals
2015/08/24 13:29:08 Sending anonymous usage statistics to m.influxdb.com - private
[continuous_querier] 2015/08/24 13:29:09 executing continuous query totals_5m
[http] 2015/08/24 13:29:13 <IP_ADDRESS> - - [24/Aug/2015:13:29:13 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - 66a4dece-4a96-11e5-8001-000000000000 287.178516ms
[http] 2015/08/24 13:29:19 <IP_ADDRESS> - - [24/Aug/2015:13:29:18 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - 69c9c11d-4a96-11e5-8002-000000000000 573.603789ms
[wal] 2015/08/24 13:29:19 Flush due to memory.  Compacting 13 series from partition 3
[wal] 2015/08/24 13:29:38 compaction of partition 3 took 3.560982945s
[wal] 2015/08/24 13:29:39 Flush due to memory. Compacting 8473 series from partition 3
[http] 2015/08/24 13:29:39 <IP_ADDRESS> - - [24/Aug/2015:13:29:39 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - 76434820-4a96-11e5-8006-000000000000 369.549142ms
[wal] 2015/08/24 13:29:40 Flush due to memory.  Compacting 66 series from partition 2
[wal] 2015/08/24 13:32:19 compaction of partition 2 took 1m3.27060289s
[wal] 2015/08/24 13:32:23 Flush due to memory. Compacting 15 series from partition 1
[wal] 2015/08/24 13:32:23 Flush due to memory. Compacting 5 series from partition 2
[wal] 2015/08/24 13:35:49 compaction of partition 1 took 3m25.979186757s
[wal] 2015/08/24 13:35:52 Flush due to memory. Compacting 4 series from partition 1
fatal error: runtime: out of memory

runtime stack:
runtime.SysMap(0xc2e48b0000, 0xc2f0000, 0x46795f800, 0xf12298)
        /root/.gvm/gos/go1.4.2/src/runtime/mem_linux.c:149 +0x98
runtime.MHeap_SysAlloc(0xf17980, 0xc2f0000, 0x431752)
        /root/.gvm/gos/go1.4.2/src/runtime/malloc.c:284 +0x124
runtime.MHeap_Alloc(0xf17980, 0x6172, 0x10100000000, 0xc26795f8c0)
        /root/.gvm/gos/go1.4.2/src/runtime/mheap.c:240 +0x66

goroutine 75 [running]:
runtime.switchtoM()
        /root/.gvm/gos/go1.4.2/src/runtime/asm_amd64.s:198 fp=0xc230223950 sp=0xc230223948
runtime.mallocgc(0xc2e2003, 0x912a20, 0x325f393100000001, 0x3d646f6874656d2c)
        /root/.gvm/gos/go1.4.2/src/runtime/malloc.go:199 +0x9f3 fp=0xc230223a00 sp=0xc230223950
runtime.newarray(0x912a20, 0xc2e2003, 0x535f4e4f49544154)
        /root/.gvm/gos/go1.4.2/src/runtime/malloc.go:365 +0xc1 fp=0xc230223a38 sp=0xc230223a00
runtime.makeslice(0x8fcf40, 0xc2e2003, 0xc2e2003, 0x0, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/runtime/slice.go:32 +0x15c fp=0xc230223a80 sp=0xc230223a38
github.com/golang/snappy.Encode(0x0 - private, 0x0, 0x0, 0xc2d8340000, 0xa70ad9e, 0xc56a000, 0x0, 0x0, 0x0)
        /root/go/src/github.com/golang/snappy/encode.go:84 - private +0xb9 fp=0xc230243b08 sp=0xc230223a80
github.com/influxdb/influxdb/tsdb/engine/wal.(*Partition).writeCompactionEntry(0xc20b5649c0 - private, 0xc2081242a8, 0xc26e1d96b0, 0x2f, 0xc2296fa000, 0x12c114, 0x15b000, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:1140 - private +0x2f0 fp=0xc230243c20 sp=0xc230243b08
github.com/influxdb/influxdb/tsdb/engine/wal.(*Partition).compactFiles(0xc20b5649c0 - private, 0xc20c8e48e0, 0x1, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:1101 - private +0x698 fp=0xc230243e50 sp=0xc230243c20
github.com/influxdb/influxdb/tsdb/engine/wal.(*Partition).flushAndCompact(0xc20b5649c0 - private, 0x1, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:1044 - private +0x6d7 fp=0xc230243fc0 sp=0xc230243e50
runtime.goexit()
        /root/.gvm/gos/go1.4.2/src/runtime/asm_amd64.s:2232 +0x1 fp=0xc230243fc8 sp=0xc230243fc0
created by github.com/influxdb/influxdb/tsdb/engine/wal.(*Partition).Write - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:787 - private +0x3f3

goroutine 1 [chan receive, 6 minutes]:
main.(*Main).Run(0xc208075b00, 0xc20800a010, 0x4, 0x4, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/main.go:91 - private +0x777
main.main()
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/main.go:42 - private +0xdc

goroutine 6 [syscall, 7 minutes]:
os/signal.loop()
        /root/.gvm/gos/go1.4.2/src/os/signal/signal_unix.go:21 +0x1f
created by os/signal.init·1
        /root/.gvm/gos/go1.4.2/src/os/signal/signal_unix.go:27 +0x35

goroutine 17 [syscall, 7 minutes, locked to thread]:
runtime.goexit()
        /root/.gvm/gos/go1.4.2/src/runtime/asm_amd64.s:2232 +0x1

goroutine 8 [IO wait, 7 minutes]:
net.(*pollDesc).Wait(0xc208010450, 0x72, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:84 +0x47
net.(*pollDesc).WaitRead(0xc208010450, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:89 +0x43
net.(*netFD).accept(0xc2080103f0, 0x0, 0x7f9fb0d84e30, 0xc208100000)
        /root/.gvm/gos/go1.4.2/src/net/fd_unix.go:419 +0x40b
net.(*TCPListener).AcceptTCP(0xc20803f188, 0x0, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:234 +0x4e
net.(*TCPListener).Accept(0xc20803f188, 0x0, 0x0, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:244 +0x4c
github.com/influxdb/influxdb/tcp.(*Mux).Serve(0xc2080e68a0 - private, 0x7f9fb0d87440, 0xc20803f188, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:45 - private +0x57
created by github.com/influxdb/influxdb/cmd/influxd/run.func·003 - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/server.go:313 - private +0x8f2

goroutine 9 [chan receive, 7 minutes]:
github.com/influxdb/influxdb/tcp.(*listener).Accept(0xc20803f190 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:117 - private +0x80
github.com/influxdb/influxdb/meta.(*raftLayer).Accept(0xc2080e69f0 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/meta/store.go:2058 - private +0x64
github.com/hashicorp/raft.(*NetworkTransport).listen(0xc208010540) - private
        /root/go/src/github.com/hashicorp/raft/net_transport.go:346 - private +0x50
created by github.com/hashicorp/raft.NewNetworkTransport - private
        /root/go/src/github.com/hashicorp/raft/net_transport.go:138 - private +0x2c4

goroutine 10 [select]:
github.com/hashicorp/raft.(*Raft).leaderLoop(0xc2080ba1c0) - private
        /root/go/src/github.com/hashicorp/raft/raft.go:826 - private +0xc7c
github.com/hashicorp/raft.(*Raft).runLeader(0xc2080ba1c0) - private
        /root/go/src/github.com/hashicorp/raft/raft.go:798 - private +0x74e
github.com/hashicorp/raft.(*Raft).run(0xc2080ba1c0) - private
        /root/go/src/github.com/hashicorp/raft/raft.go:595 - private +0xc9
github.com/hashicorp/raft.*Raft.(github.com/hashicorp/raft.run)·fm() - private
        /root/go/src/github.com/hashicorp/raft/raft.go:245 - private +0x27
github.com/hashicorp/raft.func·011() - private
        /root/go/src/github.com/hashicorp/raft/state.go:152 - private +0x51
created by github.com/hashicorp/raft.(*raftState).goFunc - private
        /root/go/src/github.com/hashicorp/raft/state.go:153 - private +0xe3

goroutine 11 [select, 6 minutes]:
github.com/hashicorp/raft.(*Raft).runFSM(0xc2080ba1c0) - private
        /root/go/src/github.com/hashicorp/raft/raft.go:502 - private +0x1043
github.com/hashicorp/raft.*Raft.(github.com/hashicorp/raft.runFSM)·fm() - private
        /root/go/src/github.com/hashicorp/raft/raft.go:246 - private +0x27
github.com/hashicorp/raft.func·011() - private
        /root/go/src/github.com/hashicorp/raft/state.go:152 - private +0x51
created by github.com/hashicorp/raft.(*raftState).goFunc - private
        /root/go/src/github.com/hashicorp/raft/state.go:153 - private +0xe3

goroutine 12 [select]:
github.com/hashicorp/raft.(*Raft).runSnapshots(0xc2080ba1c0) - private
        /root/go/src/github.com/hashicorp/raft/raft.go:1613 - private +0x466
github.com/hashicorp/raft.*Raft.(github.com/hashicorp/raft.runSnapshots)·fm() - private
        /root/go/src/github.com/hashicorp/raft/raft.go:247 - private +0x27
github.com/hashicorp/raft.func·011() - private
        /root/go/src/github.com/hashicorp/raft/state.go:152 - private +0x51
created by github.com/hashicorp/raft.(*raftState).goFunc - private
        /root/go/src/github.com/hashicorp/raft/state.go:153 - private +0xe3

goroutine 13 [select, 6 minutes]:
github.com/influxdb/influxdb/meta.(*localRaft).logLeaderChanges(0xc20800cde0) - private
        /root/go/src/github.com/influxdb/influxdb/meta/state.go:187 - private +0x46e
created by github.com/influxdb/influxdb/meta.(*localRaft).open - private
        /root/go/src/github.com/influxdb/influxdb/meta/state.go:177 - private +0x130c

goroutine 19 [chan receive, 7 minutes]:
github.com/influxdb/influxdb/tcp.(*listener).Accept(0xc20803f198 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:117 - private +0x80
github.com/influxdb/influxdb/meta.(*Store).serveExecListener(0xc208064140) - private
        /root/go/src/github.com/influxdb/influxdb/meta/store.go:619 - private +0x8f
created by github.com/influxdb/influxdb/meta.(*Store).Open - private
        /root/go/src/github.com/influxdb/influxdb/meta/store.go:239 - private +0x391

goroutine 20 [chan receive, 7 minutes]:
github.com/influxdb/influxdb/tcp.(*listener).Accept(0xc20803f1a0 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:117 - private +0x80
github.com/influxdb/influxdb/meta.(*Store).serveRPCListener(0xc208064140) - private
        /root/go/src/github.com/influxdb/influxdb/meta/store.go:723 - private +0xc9
created by github.com/influxdb/influxdb/meta.(*Store).Open - private
        /root/go/src/github.com/influxdb/influxdb/meta/store.go:242 - private +0x3db

goroutine 41 [chan receive, 6 minutes]:
github.com/influxdb/influxdb/tsdb.(*QueryExecutor).executeSelectStatement(0xc208075c40 - private, 0x0, 0xc262a652c0, 0xc262be1680, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/query_executor.go:265 - private +0xe1
github.com/influxdb/influxdb/tsdb.func·008() - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/query_executor.go:146 - private +0x6bd
created by github.com/influxdb/influxdb/tsdb.(*QueryExecutor).ExecuteQuery - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/query_executor.go:196 - private +0x1f5

goroutine 22 [select, 7 minutes]:
github.com/influxdb/influxdb/cmd/influxd/run.(*Server).monitorErrorChan(0xc2080b20e0 - private, 0xc20800c600)
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/server.go:442 - private +0x14a
created by github.com/influxdb/influxdb/cmd/influxd/run.func·003 - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/server.go:319 - private +0xa63

goroutine 50 [select]:
github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).autoflusher(0xc20817a0e0 - private, 0xc208284060)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:600 - private +0x4d3
created by github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).Open - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:219 - private +0x79b

goroutine 23 [select]:
github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).autoflusher(0xc20817a000 - private, 0xc20826a060)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:600 - private +0x4d3
created by github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).Open - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:219 - private +0x79b

goroutine 25 [runnable]:
github.com/influxdb/influxdb/services/hh.(*Service).retryWrites(0xc208063360) - private
        /root/go/src/github.com/influxdb/influxdb/services/hh/service.go:103 - private +0x2e7
created by github.com/influxdb/influxdb/services/hh.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/hh/service.go:67 - private +0x20e

goroutine 42 [running]:
        goroutine running on other thread; stack unavailable
created by github.com/influxdb/influxdb/tsdb.(*Executor).Execute - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/executor.go:90 - private +0xe3

goroutine 24 [runnable]:
github.com/influxdb/influxdb/tsdb.DedupeEntries(0xc26350d000 - private, 0x71, 0x80, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine.go:141 - private +0x19c
github.com/influxdb/influxdb/tsdb/engine/bz1.(*Engine).writeIndex(0xc2080fe340 - private, 0xc25ccad790, 0xc21086fe80, 0x74, 0xc26350d000, 0x71, 0x80, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/bz1/bz1.go:348 - private +0x34c
github.com/influxdb/influxdb/tsdb/engine/bz1.func·004(0xc25ccad790 - private, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/bz1/bz1.go:228 - private +0x3d8
github.com/boltdb/bolt.(*DB).Update(0xc20816c4e0 - private, 0xc21969fb88, 0x0, 0x0)
        /root/go/src/github.com/boltdb/bolt/db.go:547 - private +0xde
github.com/influxdb/influxdb/tsdb/engine/bz1.(*Engine).WriteIndex(0xc2080fe340 - private, 0xc26b9dab70, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/bz1/bz1.go:233 - private +0x7f
github.com/influxdb/influxdb/tsdb/engine/wal.(*Partition).flushAndCompact(0xc20b5648f0 - private, 0x1, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:1025 - private +0x456
github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).triggerAutoFlush(0xc20817a1c0) - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:584 - private +0x138
github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).autoflusher(0xc20817a1c0 - private, 0xc26671ef00)
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:605 - private +0x167
created by github.com/influxdb/influxdb/tsdb/engine/wal.(*Log).Open - private
        /root/go/src/github.com/influxdb/influxdb/tsdb/engine/wal/wal.go:219 - private +0x79b

goroutine 26 [select, 6 minutes]:
github.com/influxdb/influxdb/services/hh.(*Service).expireWrites(0xc208063360) - private
        /root/go/src/github.com/influxdb/influxdb/services/hh/service.go:121 - private +0x2a4
created by github.com/influxdb/influxdb/services/hh.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/hh/service.go:68 - private +0x228

goroutine 27 [chan receive, 6 minutes]:
github.com/influxdb/influxdb/tcp.(*listener).Accept(0xc20803f1a8 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:117 - private +0x80
github.com/influxdb/influxdb/cluster.(*Service).serve(0xc2080102a0) - private
        /root/go/src/github.com/influxdb/influxdb/cluster/service.go:83 - private +0x102
created by github.com/influxdb/influxdb/cluster.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/cluster/service.go:60 - private +0x138

goroutine 28 [select, 6 minutes]:
github.com/influxdb/influxdb/services/precreator.(*Service).runPrecreation(0xc20800adc0) - private
        /root/go/src/github.com/influxdb/influxdb/services/precreator/service.go:75 - private +0x407
created by github.com/influxdb/influxdb/services/precreator.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/precreator/service.go:53 - private +0x20a

goroutine 29 [chan receive, 6 minutes]:
github.com/influxdb/influxdb/tcp.(*listener).Accept(0xc20803f1b0 - private, 0x0, 0x0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/tcp/mux.go:117 - private +0x80
github.com/influxdb/influxdb/services/snapshotter.(*Service).serve(0xc20800aeb0) - private
        /root/go/src/github.com/influxdb/influxdb/services/snapshotter/service.go:75 - private +0xad
created by github.com/influxdb/influxdb/services/snapshotter.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/snapshotter/service.go:48 - private +0x133

goroutine 30 [IO wait, 6 minutes]:
net.(*pollDesc).Wait(0xc2117d0290, 0x72, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:84 +0x47
net.(*pollDesc).WaitRead(0xc2117d0290, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:89 +0x43
net.(*netFD).accept(0xc2117d0230, 0x0, 0x7f9fb0d84e30, 0xc217298150)
        /root/.gvm/gos/go1.4.2/src/net/fd_unix.go:419 +0x40b
net.(*TCPListener).AcceptTCP(0xc20803e118, 0xc208020700, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:234 +0x4e
net.(*TCPListener).Accept(0xc20803e118, 0x0, 0x0, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:244 +0x4c
net/http.(*Server).Serve(0xc21717aae0, 0x7f9fb0d87440, 0xc20803e118, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/http/server.go:1728 +0x92
net/http.Serve(0x7f9fb0d87440, 0xc20803e118, 0x7f9f9d8ab210, 0xc217298140, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/http/server.go:1606 +0xa1
github.com/influxdb/influxdb/services/admin.(*Service).serve(0xc20800af50) - private
        /root/go/src/github.com/influxdb/influxdb/services/admin/service.go:107 - private +0x147
created by github.com/influxdb/influxdb/services/admin.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/admin/service.go:70 - private +0x472

goroutine 31 [chan receive, 6 minutes]:
github.com/influxdb/influxdb/services/continuous_querier.(*Service).runContinuousQueryAndWriteResult(0xc208010310 - private, 0xc26285ff00, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/services/continuous_querier/service.go:299 - private +0x2c8
github.com/influxdb/influxdb/services/continuous_querier.(*Service).ExecuteContinuousQuery(0xc208010310 - private, 0xc2081e6320, 0xc262db26a0, 0x0, 0x0)
        /root/go/src/github.com/influxdb/influxdb/services/continuous_querier/service.go:249 - private +0x7ae
github.com/influxdb/influxdb/services/continuous_querier.(*Service).runContinuousQueries(0xc208010310) - private
        /root/go/src/github.com/influxdb/influxdb/services/continuous_querier/service.go:186 - private +0x32a
github.com/influxdb/influxdb/services/continuous_querier.(*Service).backgroundLoop(0xc208010310) - private
        /root/go/src/github.com/influxdb/influxdb/services/continuous_querier/service.go:168 - private +0x3ca
created by github.com/influxdb/influxdb/services/continuous_querier.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/continuous_querier/service.go:93 - private +0x2df

goroutine 32 [IO wait, 4 minutes]:
net.(*pollDesc).Wait(0xc2117d0370, 0x72, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:84 +0x47
net.(*pollDesc).WaitRead(0xc2117d0370, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/fd_poll_runtime.go:89 +0x43
net.(*netFD).accept(0xc2117d0310, 0x0, 0x7f9fb0d84e30, 0xc2172acc10)
        /root/.gvm/gos/go1.4.2/src/net/fd_unix.go:419 +0x40b
net.(*TCPListener).AcceptTCP(0xc20803e120, 0xc2080f3dc8, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:234 +0x4e
net.(*TCPListener).Accept(0xc20803e120, 0x0, 0x0, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/tcpsock_posix.go:244 +0x4c
net/http.(*Server).Serve(0xc26671f140, 0x7f9fb0d87440, 0xc20803e120, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/http/server.go:1728 +0x92
net/http.Serve(0x7f9fb0d87440, 0xc20803e120, 0x7f9f9d8ab198, 0xc208010380, 0x0, 0x0)
        /root/.gvm/gos/go1.4.2/src/net/http/server.go:1606 +0xa1
github.com/influxdb/influxdb/services/httpd.(*Service).serve(0xc20800b090) - private
        /root/go/src/github.com/influxdb/influxdb/services/httpd/service.go:108 - private +0x79
created by github.com/influxdb/influxdb/services/httpd.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/httpd/service.go:76 - private +0x68b

goroutine 33 [select, 6 minutes]:
github.com/influxdb/influxdb/services/retention.(*Service).deleteShardGroups(0xc20800ca80) - private
        /root/go/src/github.com/influxdb/influxdb/services/retention/service.go:69 - private +0x342
created by github.com/influxdb/influxdb/services/retention.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/retention/service.go:45 - private +0x138

goroutine 66 [select, 6 minutes]:
github.com/influxdb/influxdb/services/retention.(*Service).deleteShards(0xc20800ca80) - private
        /root/go/src/github.com/influxdb/influxdb/services/retention/service.go:102 - private +0x71b
created by github.com/influxdb/influxdb/services/retention.(*Service).Open - private
        /root/go/src/github.com/influxdb/influxdb/services/retention/service.go:46 - private +0x152

goroutine 67 [chan receive, 6 minutes]:
github.com/influxdb/influxdb/cmd/influxd/run.(*Server).startServerReporting(0xc2080b20e0) - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/server.go:393 - private +0x1d7
created by github.com/influxdb/influxdb/cmd/influxd/run.func·003 - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/server.go:342 - private +0xf0e

goroutine 68 [select, 6 minutes]:
github.com/influxdb/influxdb/cmd/influxd/run.(*Command).monitorServerErrors(0xc2080b4300) - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/command.go:140 - private +0x2da
created by github.com/influxdb/influxdb/cmd/influxd/run.(*Command).Run - private
        /root/go/src/github.com/influxdb/influxdb/cmd/influxd/run/command.go:122 - private +0xdef

Please try the 0.9.3-rc3.  #3836 may help but your server may be undersized for the amount of data you're writing.

I ran my test using the rc3 build.  The test ran for about an hour inserting 8,000-20,000 points every 5 seconds.  Then 500 errors occurred.  The log (see below) shows large times reported for the compaction processing.  Is seems like the compaction process can cause significant delays.  Is data compaction tune-able?  Can it be turned off?
I seems like my test server environment should be able to handle ingesting 8,000-20,000 points every 5 seconds.  That doesn't seem like a large load and top shows the process averaging 5%-20% load while ingesting data.
However, running queries in the 0.9.3 code seems to put huge loads on the server.  I have a continuous query that runs every 5 minutes.  When the query is running the server load is very high.  Simple observations comparing 0.9.3 builds to pre 0.9.3 builds shows the load caused by queries is much higher in the 0.9.3 builds.  Could the data compaction be responsible for the difference?
Note:  I have not seen a out of memory error using the 0.9.3-rc3 build which is good.
Log Snippet:
[wal] 2015/08/26 11:02:59 Flush due to memory. Flushing 5000 series with 6078503 bytes from partition 5. Compacting 30370 series
[http] 2015/08/26 11:03:07 <IP_ADDRESS> - - [26/Aug/2015:11:03:04 -0600] POST /write?db=esf&rp=rp_3d&precision=u HTTP/1.1 204 0 - - 50be3ca1-4c14-11e5-82ae-000000000000 2.767730211s
[wal] 2015/08/26 11:03:08 compaction of partition 5 took 9.452535534s
[wal] 2015/08/26 11:03:08 Flush due to memory. Flushing 4877 series with 5916799 bytes from partition 1.  Flushing 4867 series with 5934445 bytes from partition 4. Compacting 30607 series
[wal] 2015/08/26 11:03:20 compaction of partition 1 took 11.891299479s
[continuous_querier] 2015/08/26 11:03:21 wrote 729 point(s) to esf.rp_10d.totals_5m
[wal] 2015/08/26 11:03:22 compaction of partition 4 took 5.103437786s
[continuous_querier] 2015/08/26 11:03:25 wrote 729 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/26 11:03:28 wrote 729 point(s) to esf.rp_10d.totals_5m
[wal] 2015/08/26 11:04:23 Flush due to idle. Flushing 147 series with 2499 bytes from partition 1. Compacting 0 series
[wal] 2015/08/26 11:04:23 compaction of partition 1 took 53.60154ms
[wal] 2015/08/26 11:04:23 Flush due to idle. Flushing 152 series with 2584 bytes from partition 2. Compacting 0 series
[wal] 2015/08/26 11:04:23 compaction of partition 2 took 11.795046ms
[wal] 2015/08/26 11:04:23 Flush due to idle. Flushing 142 series with 2414 bytes from partition 3. Compacting 0 series
[wal] 2015/08/26 11:04:23 compaction of partition 3 took 15.526463ms
[wal] 2015/08/26 11:04:23 Flush due to idle. Flushing 141 series with 2397 bytes from partition 4. Compacting 0 series
[wal] 2015/08/26 11:04:23 compaction of partition 4 took 17.163915ms
[wal] 2015/08/26 11:04:23 Flush due to idle. Flushing 147 series with 2499 bytes from partition 5. Compacting 0 series
[wal] 2015/08/26 11:04:23 compaction of partition 5 took 15.921695ms
[continuous_querier] 2015/08/26 11:05:14 executing continuous query totals_5m
[continuous_querier] 2015/08/26 11:05:19 wrote 729 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/26 11:05:22 wrote 729 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/26 11:05:22 executing continuous query totals_1h
[continuous_querier] 2015/08/26 11:05:22 wrote 729 point(s) to esf.rp_30d.totals_1h
[continuous_querier] 2015/08/26 11:05:22 wrote 729 point(s) to esf.rp_30d.totals_1h
[continuous_querier] 2015/08/26 11:07:15 executing continuous query totals_5m
[continuous_querier] 2015/08/26 11:07:20 wrote 729 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/26 11:07:24 wrote 729 point(s) to esf.rp_10d.totals_5m
[wal] 2015/08/26 11:08:18 Flush due to idle. Flushing 31650 series with 15166482 bytes from partition 1. Compacting 0 series
[wal] 2015/08/26 11:08:33 compaction of partition 1 took 15.332402358s
[wal] 2015/08/26 11:08:33 Flush due to idle. Flushing 34904 series with 15332861 bytes from partition 2. Compacting 0 series
[wal] 2015/08/26 11:08:52 compaction of partition 2 took 18.930611853s
[wal] 2015/08/26 11:08:52 Flush due to idle. Flushing 35216 series with 20826224 bytes from partition 3. Compacting 0 series
[retention] 2015/08/26 11:09:08 retention policy enforcement check commencing
[retention] 2015/08/26 11:09:08 retention policy shard deletion check commencing
[continuous_querier] 2015/08/26 11:09:15 executing continuous query totals_5m
[wal] 2015/08/26 11:09:18 compaction of partition 3 took 25.753009376s
[wal] 2015/08/26 11:09:18 Flush due to idle. Flushing 31264 series with 15124577 bytes from partition 4. Compacting 0 series
[continuous_querier] 2015/08/26 11:09:25 wrote 729 point(s) to esf.rp_10d.totals_5m
[wal] 2015/08/26 11:09:25 compaction of partition 4 took 7.341834024s
[wal] 2015/08/26 11:09:25 Flush due to idle. Flushing 31834 series with 15060113 bytes from partition 5. Compacting 0 series
[wal] 2015/08/26 11:10:23 Flush due to idle. Flushing 147 series with 4998 bytes from partition 1. Compacting 0 series
[wal] 2015/08/26 11:10:23 compaction of partition 1 took 315.81059ms
[wal] 2015/08/26 11:10:23 Flush due to idle. Flushing 152 series with 5168 bytes from partition 2. Compacting 0 series
[wal] 2015/08/26 11:10:23 compaction of partition 2 took 53.157876ms
[wal] 2015/08/26 11:10:23 Flush due to idle. Flushing 142 series with 4828 bytes from partition 3. Compacting 0 series
[wal] 2015/08/26 11:10:23 compaction of partition 3 took 35.017204ms
[wal] 2015/08/26 11:10:23 Flush due to idle. Flushing 141 series with 4794 bytes from partition 4. Compacting 0 series
[wal] 2015/08/26 11:10:23 compaction of partition 4 took 69.799069ms
[wal] 2015/08/26 11:10:23 Flush due to idle. Flushing 147 series with 4998 bytes from partition 5. Compacting 0 series
[wal] 2015/08/26 11:10:23 compaction of partition 5 took 34.973182ms
[continuous_querier] 2015/08/26 11:11:23 wrote 729 point(s) to esf.rp_10d.totals_5m
[continuous_querier] 2015/08/26 11:11:23 executing continuous query totals_1h
[continuous_querier] 2015/08/26 11:11:23 wrote 729 point(s) to esf.rp_30d.totals_1h
[continuous_querier] 2015/08/26 11:11:28 executing continuous query totals_5m
[wal] 2015/08/26 11:11:46 compaction of partition 5 took 2m21.410514108s

#3853 should help with the compaction times and time outs.

Thanks for the information.  #3853 looks promising.  Do you know if #3853 will make it into the 0.9.3 builds?

Yes, the change will be part of the 0.9.3 release.
On Wednesday, August 26, 2015, dsw6<EMAIL_ADDRESS>wrote:

Thanks for the information. #3853
https://github.com/influxdb/influxdb/pull/3853 looks promising. Do you
know if #3853 https://github.com/influxdb/influxdb/pull/3853 will make
it into the 0.9.3 builds?
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/3835#issuecomment-135146066.

Awesome.  I'll watch for change #3853 to make it into an rc build and I'll run some more tests.

@dsw6 0.9.3 is out now, can you test again?

A quick note that compactions do not block writes in any way. That said, if you want to increase the frequency of compactions and flushes you can tune some WAL settings: https://github.com/influxdb/influxdb/blob/master/etc/config.sample.toml#L46-L68
Specifically, lower wal-ready-series-size to force frequently sampled series to flush more often. Also you can lower wal-partition-size-threshold to force partitions to compact more frequently.

I ran my test again using the 0.9.3 release build.  The test ran for about one hour and then received a 500 error from a write operation.  During the test, I monitored the memory usage for the influxDB process.  Memory usage started low and continued to steadily grow throughout the test.  Memory usage was around 95% when the 500 error occurred.  I configured the test to stop on the first 500 error.  Several minutes of no activity and  memory usage remained high at 95%.
I shutdown the influxDB process.  Upon restarting influxDB, memory usage quickly climbed to 60% (no tests running).  After a few minutes, memory usage stabilized around 30%.  I restarted my tests.  The tests ran for about 40 minutes and received a 500 error.  influxDB memory usage was 93%.

Hi,
I'm also having an "out of memory" issue, and I hope this info can help.
If this is not related to this issue please move to the correct issue or create a new one.
When trying to drop a measurement:
[http] 2015/09/10 11:49:57 <IP_ADDRESS> - - [10/Sep/2015:11:49:57 +0000] OPTIONS /query?q=DROP+MEASUREMENT+%221-opt_cachequeue_clean%3E100%22&db=support HTTP/1.1 200 0 http://<IP_ADDRESS>:8083/? Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36 0f125019-57b2-11e5-9b93-000000000000 30.032µs
fatal error: runtime: out of memory

At this point I can't even start InfluxDB service because after starting the service the 8GB memory are completely exhausted in 12 seconds and ends with an "out of memory" error.
[metastore] 2015/09/10 12:52:40 Using data dir: /opt/influxdb/meta
[metastore] 2015/09/10 12:52:40 Node at <IP_ADDRESS>:8088 [Follower]
[metastore] 2015/09/10 12:52:40 Skipping cluster join: already member of cluster: nodeId=1 raftEnabled=true peers=[<IP_ADDRESS>:8088]
[store] 2015/09/10 12:52:40 Using data dir: /opt/influxdb/data
[wal] 2015/09/10 12:52:41 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:41 WAL writing to /opt/influxdb/wal/collectd/collectdpolicy/20
[wal] 2015/09/10 12:52:42 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:42 WAL writing to /opt/influxdb/wal/collectd/collectdpolicy/36
[metastore] 2015/09/10 12:52:42 Node at <IP_ADDRESS>:8088 [Leader]. peers=[<IP_ADDRESS>:8088]
[metastore] 2015/09/10 12:52:42 Node at <IP_ADDRESS>:8088 [Follower]. peers=[<IP_ADDRESS>:8088]
[metastore] 2015/09/10 12:52:44 Updated node id=1 hostname=<IP_ADDRESS>:8088
[metastore] 2015/09/10 12:52:44 Node at <IP_ADDRESS>:8088 [Leader]. peers=[<IP_ADDRESS>:8088]
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/support/default/21
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/support/default/22
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/support/default/37
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/test/default/139
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/test/default/38
[wal] 2015/09/10 12:52:52 WAL starting with 30720 ready series size, 0.50 compaction threshold, and 20971520 partition size threshold
[wal] 2015/09/10 12:52:52 WAL writing to /opt/influxdb/wal/test/testpolicy/191
[handoff] 2015/09/10 12:52:52 Starting hinted handoff service
[handoff] 2015/09/10 12:52:52 Using data dir: /var/opt/influxdb/hh
[tcp] 2015/09/10 12:52:52 Starting cluster service
[shard-precreation] 2015/09/10 12:52:52 Starting precreation service with check interval of 10m0s, advance period of 30m0s
[snapshot] 2015/09/10 12:52:52 Starting snapshot service
[admin] 2015/09/10 12:52:52 Starting admin service
[admin] 2015/09/10 12:52:52 Listening on HTTP: [::]:8083
[continuous_querier] 2015/09/10 12:52:52 Starting continuous query service
[httpd] 2015/09/10 12:52:52 Starting HTTP service
[httpd] 2015/09/10 12:52:52 Authentication enabled: true
[httpd] 2015/09/10 12:52:52 Listening on HTTP: [::]:8086
[collectd] 2015/09/10 12:52:52 Starting collectd service
[collectd] 2015/09/10 12:52:52 Listening on UDP:  [::]:25826
[retention] 2015/09/10 12:52:52 Starting rentention policy enforcement service
2015/09/10 12:52:52 InfluxDB starting, version 0.9.3-rc2, branch 0.9.3, commit d0646a8871a583f8342afd0dc1a253946565d2cd
2015/09/10 12:52:52 GOMAXPROCS set to 2
[run] 2015/09/10 12:52:52 Listening for signals
2015/09/10 12:52:52 Sending anonymous usage statistics to m.influxdb.com
[wal] 2015/09/10 12:52:53 Flush due to memory. Compacting 979 series from partition 4
fatal error: runtime: out of memory

After a bunch of testing, we've determined that the underlying index just can't keep up with the insertion load that the WAL makes possible. To prevent the system from going OOM and dying we're going to put back pressure on the write clients and start failing writes when memory gets too high. See #4066.
We're also working on a massive storage engine upgrade that will fix this. Should be available in the nightlies within a week or two. It will have much better compression and be able to keep up with the write load of the WAL.
More soon...

Closing this out to consolidate things. Track #4086 for when this is done.


feat(CategoryTheory): the monoidal category structure on graded objects

Under suitable conditions on a monoidal category C, we define an instance of MonoidalCategory (GradedObject ℕ C). The construction is actually more general, and it shall be used in order to get monoidal category structures on homological complexes in future PRs.
Co-authored-by: Kim Morrison<EMAIL_ADDRESS>

[x] depends on: #14343

Excited to see that you've finished this @joelriou, it's great!
bors d+

Thanks!
bors merge


colorFilters don't work on fuchsia with vulkan enabled.

This code doesn't appear to apply the color filter.
    return new Container(
      decoration: new BoxDecoration(
        backgroundColor: Colors.black,
        backgroundImage: new BackgroundImage(
          image: new AssetImage(_kBackgroundImage),
          alignment: const FractionalOffset(0.4, 0.5),
          fit: BoxFit.cover,
          colorFilter: new ui.ColorFilter.mode(
            _kBackgroundOverlayColor,
            ui.BlendMode.srcATop,
          ),
        ),
      ),
      child: currentChild,
    );

Probably a missing feature in Skia's Vulkan backend.  /cc @chinmaygarde

@apwilson Please mark this as a blocker if you need this fixed sooner. Thanks.

@apwilson We believe there's a good chance this is fixed now. Please let us know if it is not.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Require etc library

Description
Many other packages require etc but when using chef-config directly without requiring etc first, the code fails with a NameError at runtime. This only happens inconsistently and varies by ruby version because many other tools and packages require etc.
~/scratch $ ruby --version
ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin19]
~/scratch $ irb

WARNING: This version of ruby is included in macOS for compatibility with legacy software.
In future versions of macOS the ruby runtime will not be available by
default, and may require you to install an additional package.

irb(main):001:0> Etc.getlogin
Traceback (most recent call last):
        4: from /usr/bin/irb:23:in `<main>'
        3: from /usr/bin/irb:23:in `load'
        2: from /Library/Ruby/Gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        1: from (irb):1
NameError (uninitialized constant Etc)
~/scratch $ cat etc_test.rb
#!/usr/bin/env ruby

begin
  Etc.getlogin
rescue
  puts "#{$!.class}: #{$!.message}"
end

require "etc" unless defined?(Etc)

begin
  puts(Etc.getlogin.length)
rescue
  puts $!.message
end
~/scratch $ ./etc_test.rb
NameError: uninitialized constant Etc
4
~/scratch $ source ~/envs/ruby3.1/bin/activate.sh
~/scratch $ ruby --version
ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-darwin19]
~/scratch $ ./etc_test.rb
NameError: uninitialized constant Etc

  Etc.getlogin
  ^^^
4
~/scratch $ irb
irb(main):001:0> Etc.getlogin.length
=> 4

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@curzonj Can you provide an example within the context of using chef-config in which the NameError occurs?


Add filter to check validity of CITATION.cff followup

Description
Took another stab at #4 based off @fdiblen 's earlier PR #47 . Resulting set of URLs is the same as what @abelsiqueira showed earlier, but with code I can understand more easily.
Related issues:

#4

Instructions to review the pull request

Make a GitHub Access token here https://github.com/settings/tokens

Make sure you copy it when it appears on screen, because you can't see it again. You can reset it, though.

export GITHUB_TOKEN as an environment variable with the token above
install Node >= 14

cd $(mktemp -d --tmpdir cffbot-XXXXXX)
git clone https://github.com/cffbots/filtering .
git checkout <this-branch>
npm install
node query.mjs

conflicts resolved, thanks for the review Abel


fix: Upgrade dependancies to avoid security warnings

Description
Upgrades lodash and set-values to avoid critical and high security warning
Task Item
#minor

Coverage remained the same at 40.503% when pulling 5cb4e5bf6d3945474ff427b3e03870781ead9966 on srravich/security-fix into 069fe49c923db0679b3e8b1cc661a911078a0a60 on master.


treyBake: Watch GeekBee.io

treyBake requests the watch of the watch_keyword GeekBee\.io. See the MS search here and the Stack Exchange search here.

GeekBee\.io has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Banner ads

your idea is good but why not banner ads. if possible then also do that. any way cheers for your efforts!

We can probably allow using a hardcoded dimension (320x50) sized Banner.
See this, but ADAPTIVE & SMART Banner won't be the main focus right now.
Re-Opening this for next feature request.


spring.cloud.config.server.bootstrap bug

I write a spring cloud config server, whose bootstrap.properties is as follows:
spring.cloud.config.server.bootstrap=true
spring.application.name=config-server
spring.profiles.active=native

However, enabling spring.cloud.config.server.bootstrap will incur a bug that the config server will use the configurations in its application.properties as the common external configs of all the clients. This can be observed by visiting certain url:

Here, my config server runs at localhost:9090 and web-server is the name of config client. All the propertyResources are from config server's application.properties actually.
spring-cloud-config version: 1.4.1

So without spring.cloud.config.server.bootstrap=true this bug does not appear?

It might have to do with native

Right but from what the documentation says it seems like we would expect all properties from application.properties to be removed.

@ryanjbaxter yes, nothing goes wrong without spring.cloud.config.server.bootstrap=true. I have not tested that whether this bug appears when using non-native repository.

This was a tough one to figure out the root cause.  It is a little complicated so here we go.
It all has to do with when NativeRepositoryConfiguration is created.  When spring.cloud.config.server.bootstrap=true NativeRepositoryConfiguration is created during the bootstrap phase (very early on when the application is started up) and before this line of code is run
https://github.com/spring-cloud/spring-cloud-commons/blob/v1.3.2.RELEASE/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/BootstrapApplicationListener.java#L192
In this case NativeRepositoryConfiguration is created here https://github.com/spring-cloud/spring-cloud-commons/blob/v1.3.2.RELEASE/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/BootstrapApplicationListener.java#L187
The reason it is created here is because ConfigServerBootstrapConfiguration imports EnvironmentRepositoryConfiguration which imports NativeRepositoryConfiguration and ConfigServerBootstrapConfiguration is only run when spring.cloud.config.server.bootstrap=true as you can see here https://github.com/spring-cloud/spring-cloud-config/blob/v1.4.2.RELEASE/spring-cloud-config-server/src/main/java/org/springframework/cloud/config/server/bootstrap/ConfigServerBootstrapConfiguration.java#L44.  When NativeEnvironmentRepository is created this early on the application.yml has not yet been added as a property source to the environment.  So the Environment variable in NativeEnvironmentRepository does not contain that property source.  This means when the code in NativeEnvironmentRepository.clean runs it won't fine application.yml in the Environment and will include it in the response to the client.
https://github.com/spring-cloud/spring-cloud-config/blob/v1.4.2.RELEASE/spring-cloud-config-server/src/main/java/org/springframework/cloud/config/server/environment/NativeEnvironmentRepository.java#L214
When NativeEnvironmentRepository is not instantiated during the bootstrap phase, ie when spring.cloud.config.server.bootstrap is not set to true, then this line of code has a chance to run https://github.com/spring-cloud/spring-cloud-commons/blob/v1.3.2.RELEASE/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/BootstrapApplicationListener.java#L192
What this will do is remove spring.config.name=bootstrap from the environment.  Then when this line of code runs in ConfigFileApplicationListener
https://github.com/spring-projects/spring-boot/blob/v1.5.10.RELEASE/spring-boot/src/main/java/org/springframework/boot/context/config/ConfigFileApplicationListener.java#L644
application will be returned and it will pickup application.yml and add it to the PropertySources in the Environment.  Now when NativeEnvironmentRepository is instantiated the Environment variable will contain the application.yml and will not include it when clean is run.
After thinking about this for a while I think this all makes sense given that when spring.cloud.config.server.bootstrap=true this will mean that the config server is looking to configure itself from the configured environment repository.  In order to do that it would need application.yml to be returned because it is a client of itself.  But because you are using a native repository and have not set any search locations its going to include what is on the classpath.  If you set a search location that did not include the classpath it would not include the application.yml.
I hope that all makes sense :)


Flex positioning of items with different widths

Consider this code from the docs:

Flex item

Flex item

Longer Longer Flex item

I would like to always keep the second item centered even if the third (or the first) item is wider.
I'm trying to make a navbar with this layout but I can't find a way to keep the central item centered regardless of the others.

Regrettably, that's just not possible with flexbox alone. The only way to accomplish that is forcing equal width on the first and last elements, or using absolute positioning. Here's a demo of using absolute position and flex styles. Please bear in mind, however, that this isn't bulletproof and might cause other issues.


matplotlib build fails on macOS

Issue description
matplotlib-2.0.2 gets about halfway through its build and fails an assertion test due to floating point rounding error.
All other tests are completely fine up until then. Unfortunately I simply don't know how to override the test in this case.
`packageOverrides = pkgs: with pkgs; {
myPythonEnv = python36.withPackages(ps: with ps; [numpy astropy ipython scipy cython matplotlib]);
};`
Steps to reproduce
Build matplotlib or specify it as input to python35/python36 build.
Technical details

System: macOS Sierra 10.12.5
Nix version: nix-1.11.7
Nixpkgs version: "17.09pre108026.7596d21f69"
Sandboxing enabled: No

can you tell which exact test it is?

All tests run on NixOS with 3.6.

Sorry for the command line dump, but here is the terminal output:
`post-installation fixup
stripping (with flags -S) in /nix/store/gx8zd4g78rm7zqymwj45c68j1kbg2j2x-python3.6-simplejson-3.8.1/lib
patching script interpreter paths in /nix/store/gx8zd4g78rm7zqymwj45c68j1kbg2j2x-python3.6-simplejson-3.8.1
running install tests
running test
/nix/store/y3w8qnkn9py20lb8kpipn0pr440h5zgp-python3.6-setuptools-30.2.0/lib/python3.6/site-packages/site.py:26: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp  # Avoid import loop in Python >= 3.3
...................................................F.................ss...................................................s
FAIL: test_floats (simplejson.tests.test_float.TestFloat)
Traceback (most recent call last):
File "/private/var/folders/by/mw_ml3rx2hg25s45hc_j5_fm0000gn/T/nix-build-python3.6-simplejson-3.8.1.drv-0/simplejson-3.8.1/simplejson/tests/test_float.py", line 26, in test_floats
self.assertEqual(float(json.dumps(num)), num)
AssertionError: 1.9275814160560202e-50 != 1.9275814160560206e-50

Ran 123 tests in 1.242s
FAILED (failures=1, skipped=3)
builder for ‘/nix/store/9w27l8pkp69rg1d9crc3jc3kycyi8ky2-python3.6-simplejson-3.8.1.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/pi8sjx92sfngaiw3rl6f4pwda543ajgi-python3.6-Sphinx-1.5.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/gmkdmmmf8hgnc6hziva1bz0lkna765yi-python3.6-matplotlib-2.0.0.drv’: 1 dependencies couldn't bebuilt
cannot build derivation ‘/nix/store/yssxvk459qx8crc340nwzx0c0q67spn3-python3-3.6.1-env.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/yssxvk459qx8crc340nwzx0c0q67spn3-python3-3.6.1-env.drv’ failed`
It's simple floating point rounding error, I'm just not sure how I can override this test.

Here is the terminal dump:
'''
post-installation fixup
stripping (with flags -S) in /nix/store/gx8zd4g78rm7zqymwj45c68j1kbg2j2x-python3.6-simplejson-3.8.1/lib
patching script interpreter paths in /nix/store/gx8zd4g78rm7zqymwj45c68j1kbg2j2x-python3.6-simplejson-3.8.1
running install tests
running test
/nix/store/y3w8qnkn9py20lb8kpipn0pr440h5zgp-python3.6-setuptools-30.2.0/lib/python3.6/site-packages/site.py:26: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp  # Avoid import loop in Python >= 3.3
...................................................F.................ss...................................................s
FAIL: test_floats (simplejson.tests.test_float.TestFloat)
Traceback (most recent call last):
File "/private/var/folders/by/mw_ml3rx2hg25s45hc_j5_fm0000gn/T/nix-build-python3.6-simplejson-3.8.1.drv-0/simplejson-3.8.1/simplejson/tests/test_float.py", line 26, in test_floats
self.assertEqual(float(json.dumps(num)), num)
AssertionError: 1.9275814160560202e-50 != 1.9275814160560206e-50

Ran 123 tests in 1.242s
FAILED (failures=1, skipped=3)
builder for ‘/nix/store/9w27l8pkp69rg1d9crc3jc3kycyi8ky2-python3.6-simplejson-3.8.1.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/pi8sjx92sfngaiw3rl6f4pwda543ajgi-python3.6-Sphinx-1.5.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/gmkdmmmf8hgnc6hziva1bz0lkna765yi-python3.6-matplotlib-2.0.0.drv’: 1 dependencies couldn't bebuilt
cannot build derivation ‘/nix/store/yssxvk459qx8crc340nwzx0c0q67spn3-python3-3.6.1-env.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/yssxvk459qx8crc340nwzx0c0q67spn3-python3-3.6.1-env.drv’ failed
'''
It just looks like standard floating point rounding error to me.

can you try with https://github.com/NixOS/nixpkgs/commit/d0f2361bc1ffdff631fc7ebb9c2ec1b08b135898?

I did, and unfortunately it doesn't work :(
Looks like this might be an upstream issue for SimpleJson on Darwin?
I think cython has a dodgy unit test on darwin too, and you are able to run a hook that pulls the wrong result out and subs a dummy one in to get it to finish and build successfully. Unfortunately that is way beyond my knowledge of nix.

I can imagine upstream doesn't test on Darwin as much. I recommend you report the issues upstream. For here in Nixpkgs you could

report the issues and, even better, try to fix them
discuss with Darwin maintainers about possibly disabling tests altogether, though that should be an absolute last resort.

Yeah I guess I'll fix it, but I think this issue should be closed until I can generate a PR and useful commit.

Okay so I've been looking into this more now. The source downloaded and installed manually sans-Nix  perfectly fine. It also builds fine. Something about the nix build step is causing a tiny floating point error which is throwing off the test.
Is there a hook to selectively disable the tests for just this module? Disabling all tests on Darwin I feel is far too hamfisted.
I re-built it in an isolated as possible system and no change unfortunately. I am not sure if its a problem with my specific nix install but I doubt it. I'd be interested to hear if anyone has had this problem, because this breaks a load of pretty popular packages on Darwin.
But if its built outside of nix, then there is seemingly no problem. Which is weird.

Pass doCheck = !stdenv.isDarwin;

Okay that seems to work, Pr submitted. #26405


background model gives bad results for unbounded scene

Hello and thank you for your great work.
I tried running nerf on a scene from the unbounded 360 dataset. I use the nerf-colmap yaml as config file. In the readme, you mention that testing does nothing but compare to white images. Therefore, the model would simply overfit to all images provided. I changed the dataloader to evaluate novel views with the model. The only change was selecting some images as training views and others for testing, with a ratio of 0.5.
The result is very bad for testing views in this case (the generated images are too blurry and lacks fine details) also the depth map is messed up. I don't think that the performance should deteriorate as much. Have you tested the background model for the task of novel view synthesis ?
I also noticed that you don't get an exported mesh even when overfitting to all views, I wonder if it's related since it is the density field that is used for marching cubes as far as I can tell.

Hi! I think the ratio 0.5 is too high for these 360 scenes, maybe you should try 0.1 or 0.2. The mesh not being correctly exported could result from (1) the scene does not have solid geometry like in your case; (2) you may need to tweak the isosurface threshold in order to get good results.

Hi, thanks for the reply. Actually, this is a problem I'm encountering even with the dtu dataset. In the neus paper, they show that it can reach good performance for novel view synthesis task but here it is not the case. it is even more problematic without a mask and when using the background model. One thing I found that somehow improve results is commenting the line comp_rgb = comp_rgb + self.background_color * (1.0 - opacity) . I'm not sure why it helps though. any idea regarding this ?

I encounter the same issue. The background model is problematic within the NeuS framework.


Changed mac/linux path to match windows

Changelog:
Issue: Path for linux/mac was incorrect
Solution: Changed to match windows path
(I don't really know the styles to write these sorry)

:heart:


[docs] Update readme links and reformat screenshot

The Issue
I came across two random things to fix.
How This PR Solves The Issue
This spiffs up a recently-added image and fixes some URLs in the readme. That’s it.
Manual Testing Instructions
Preview changes locally or inspect the automatic build.
Automated Testing Overview
n/a
Related Issue Link(s)

#4188

Release/Deployment Notes
n/a

Will pull when you say.

Whenever you’d like!


I don't find the args.encoder_adapter_depths  to be used in the all projects？

args.if_mask_decoder_adapter=True
args.if_encoder_adapter=True
# You can pick the image encoder blocks by adding adapters
args.encoder_adapter_depths = range(0,12)

Hi, i might not fully understand your question here. if you are using encoder_adapter_depth, it means you would like to use Adapter for fine-tune the model; thus for the other fine-tune methods such as only update decoder/ or use LoRA; this args.encoder_adapter_depths is not used.
Also, for different Encoder architecture, you need to edit the args.encoder_adapter_depths accordingly, such as for vit-h, you need to do range(0,32).
If you are asking where in my piece of code i am referring to this args to add Adapters, it is in sam/modeling/image_encoder.py.

Generally, it refers to the args.if_encoder_adapter and (self.depth in self.args.encoder_adapter_depths).
Please let me know if this answers your question, and feel free to add additional comments!!

Thank you very much!


Build error with refit.targets(29,5).

I have the following error while trying to build my application :
refit.targets(29,5): error : Object reference not set to an instance of an object.
The correponding line is the following :
I did not found any issue relative to this particular error.
I am targetting dotnetcore 2.0 on Windows 10 and it's a simple console application that I was just using to test refit.
Could it be a configuration issue with my project ?

Do you have a repro? Can you share your project?

It was just a simple project  to test refit. I shared my code on https://bitbucket.org/anedelec/testlib/src

I don't know if Paket works. You don't need Paket anymore with the modern Csproj format.
Can you remove that and try adding a <PackageReference Include="Refit" Version="4.0.0" /> and let me know if that fixes it.

That was it. It is building correctly using Nuget, but I don't understand why. Packet is supposed to work correctly and retrieve packages from nuget. It brings other features that can be interesting so it's too bad it is not working, I may have configured it badly.


feat(dependabot): create dependabot configuration

Refs https://github.com/sap-linuxlab/community.sap_install/discussions/421
Dependabot version updates must be enable via the security tab

Is this an alternative to creating the issue or is it complementing it?

No this is an alternative solution to the pr#657, the main difference are:

pr#657 can be maintain by us with feature provided by us
pr#657 can now open only issues, but I can improve to open pr
this pr is about dependabot that is a github product that open pr only without issues
I think that there are no best solution, but dependabot is the one that we can leave as it is and works because is maintain by github itself.

@Wabri I prefer having issues opened instead of PRs, so this appears to be an advantage over dependabot. Also the feature of creating an issue only once, even if an issue has been closed without solving the dependency, is very useful. It's because we may decide in some cases to stick to a specific outdated version longer.
@kksat Are aware of any advantages of dependabot we have not covered yet in this issue?

So far, I found https://github.com/renovatebot/renovate/commit/5960b5339ac485796ac8d05ad2ad9b037f0fbc5b as comparison between dependabot and renovatebot.

@berndfinger I see opening issues instead of PRs as disadvantage. If PR is opened to update version of ansible-lint, and ansible-lint is running as CI. One can immediately see all the new failures and estimate how long will it take to fix them.
With issues, just more work to manually create PR, same work to fix all the issues anyway.
I have really good experience with dependabot, it is really a pleasure merging automatically created PRs.

Getting a PR opened for every dependency change will most likely cause a lot of overhead for role maintainers. Considering the frequency at which ansible-lint changes and the effect it usually has, it would be annoying to increase the frequency at which we have to work through all roles' new lint complaints.
I suggest we rather let it open issues, test the impact on the collection and then plan the related work ahead.

Both approaches are fine. But I think we should use the dependabot over a script because of the following reasons.

Openening a PR for new dependencies is a good practices. The maintainers should always know the latest versions of e.g. ansible-lint and make sure everything works with newer versions.
Ignoring new Versions could be achieved by closing the pr as well.
We should more likely define workflows which runs automatically on new PRs to test with the new dependency. If there are no errors the PR could merged either automatically or manually without any issue.
The script and the container where the script runs, must be maintained as well. The Bot is maintained by GitHub.
I think the integration effort for a created issue to raise new Versions is more than just have a PR where all packages are updated.

There are way more reasons for the dependeabot instead this script but I think my preference is clear :-)

I really do not want to have many PRs opened by dependabot. We will probably have more dependent tools in GitHub actions over the next weeks and months and getting too many PRs just for this purpose will delay our development. We better focus on the real work and do a version bump of dependent tools for example every 3 or 6 months.
I think we could give dependabot a try if:

we let it run just once per week
if we only run it against the dev tree (similar to https://github.com/sap-linuxlab/community.sap_install/blob/7c36fea31c695f4a5443bf806d71e613275c4170/.github/dependabot.yml#L10), so it seems that it easyly possible
all changes go into one PR which is always updated using the latest dev tree until we finally (e.g. after 3 or 6 months) merge it into the dev tree

@Wabri Do you know if/think the above is possible?

@berndfinger if the question is: could dependabot use only one pr to do the dependency update request? the answer is no. Dependabot will open one pr for every outdated package, I dont know how it acts when it open a pr that remain pending for a long time and a new version cames out. I'll investigate more about this.
If we want to try dependabot we can merge this pr and let it run for a while, I dont think it will be a problem if it open a couple of pr.

@berndfinger if the question is: could dependabot use only one pr to do the dependency update request? the answer is no. Dependabot will open one pr for every outdated package, I dont know how it acts when it open a pr that remain pending for a long time and a new version cames out. I'll investigate more about this.
If we want to try dependabot we can merge this pr and let it run for a while, I dont think it will be a problem if it open a couple of pr.

I agree - We could start trying out. However, if we already know that we will get many PRs, we have created some unnecessary additional work. So we better spend a little bit more time to get it right initially as much as possible.
In the meantime, I found in the dependabot documentation that we can use the parameter open-pull-requests-limit to limit the amount of open PRs. If we set this limit to two, we would quickly see after the first PR that a new dependency update has been detected and then we could either close it and wait for the next one to be opened, or if we think it's critical start working on both.
It seems however that after a PR is closed without merging, dependabot will not include the previously detected updates in the consecutive runs. I found a related discussion here - the original post also mentioned a PR limit of 2. But it seems this problem has not yet been solved.

Update with the PR limit 👍

Dependabot cannot be trigger manually, I will do more tests to find a solution!


[GSSoC 23'] Added SignIN GUI with verification

Thank you, @Pranjal360Agarwal, for providing me with the opportunity to contribute to your repository. I am glad to inform you that I have successfully added the SignIn Page to your code. This new feature allows the program to check the username and password from the database. Since I was unsure about the specific type of database your program utilizes, I have temporarily utilized the File system to store the data. I hope this addition meets your expectations and proves to be beneficial. If you have any further feedback or requirements, please let me know.

Hi @Pranjal360Agarwal, here are some previews of changes I made to the repo
SignIN page preview

If the entered Password and Username are incorrect then it shows a pop-up

If the entered Password and Username are correct then it is redirected to


Support CSS 2.1 headings pattern

#1221 covers regular definitions. A bigger problem is that CSS 2.1 follows a different pattern for headings, through the use of <a name> anchors within heading elements to create an ID.
The crawler does not expect that. The lack of IDs in the heading elements affects the extraction of the headings themselves and the creation of a spec outline with identifiers.

Headings should now be properly extracted.


⚠ Thumbnails API Endpoint has degraded performance

In a6d3b55, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1091 ms

Resolved: Thumbnails API Endpoint performance has improved in c1b02b3 after 9 minutes.


[Feature] Consistent cross-browser behavior of number input step buttons

Bug, feature request, or proposal:
Feature request/proposal
What is the expected behavior?
All browsers handle <input type="number"> very inconsistently.
Firefox and Safari show a "step up" and "step down" button at all times.
Chrome shows the buttons only during hover or focus on the element.
Internet Explorer and Edge have no such buttons.
In addition, Firefox, Chrome, and Safari support .stepUp() and .stepDown() on HTMLInputElements while Internet Explorer and Edge do not.
The buttons provided by Firefox, Chrome, and Safari have a style that is very inconsistent with Material.
I suggest mimicing these buttons in a cross-browser compatible way but with a "Material" style.
What is the current behavior?
Currently, these buttons are handled by the browser and behave/look very inconsistent.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-e9juzn
This is my functional mock-up of the behavior I have in mind. My code is probably hackish but the end result is nice.
HTML:
<mat-form-field>
  <mat-label>Some Quantity</mat-label>
  <input matInput #someQuantityInput [(ngModel)]="someQuantity" type="number"/>

</mat-form-field>

SCSS:
@import '~@angular/material/theming';

// use these to test with dark theme
@import<EMAIL_ADDRESS>$primary: mat-palette($mat-pink, 700, 500, 900);
$accent:  mat-palette($mat-blue-grey, A200, A100, A400);
$default: rgba(255, 255, 255, 0.7);
$disabled: rgba(255, 255, 255, 0.5);

// use these to test with light theme
// @import<EMAIL_ADDRESS>// $primary: mat-palette($mat-indigo);
// $accent:  mat-palette($mat-pink, A200, A100, A400);
// $default: rgba(0, 0, 0, 0.54);
// $disabled: rgba(0, 0, 0, 0.38);

$warn: mat-palette($mat-red);

// hide step buttons on Firefox
input[type=number] {
    -webkit-appearance: textfield;
    -moz-appearance: textfield;
    appearance: textfield;
}

// hide step buttons on Chrome/Safari
input[type=number]::-webkit-inner-spin-button,
input[type=number]::-webkit-outer-spin-button {
    -webkit-appearance: none;
    -moz-appearance: none;
    appearance: none;
}

// workaround for Firefox bug where disabled number input with textfield appearance is still clickable
.mat-form-field.mat-form-field-disabled {
    pointer-events: none;
}

// shorten the textbox to make room for step-arrow-wrapper
input[type=number] {
    width: calc(100% - 18px);
}

// shorten the mat-label to make room for step-arrow-wrapper
// (doesn't work inside stackblitz but does work otherwise)
::ng-deep .step-arrow-wrapper + .mat-form-field-label-wrapper {
    width: calc(100% - 18px);
}

// place step-arrow-wrapper to the right of textbox
.step-arrow-wrapper {
    float: right;
    width: 18px;
}

// step arrow style made to match mat-select arrow
.step-up-arrow,
.step-down-arrow {
    cursor: pointer;
    width: 0;
    height: 0;
    border-left: 5px solid transparent;
    border-right: 5px solid transparent;
    margin: 0 4px;
    color: $default;
}

.step-up-arrow {
    border-bottom: 5px solid;
    margin-bottom: 5px;
}

.step-down-arrow {
    border-top: 5px solid;
}

.mat-form-field.mat-focused.mat-primary .step-up-arrow,
.mat-form-field.mat-focused.mat-primary .step-down-arrow {
    color: mat-color($primary);
}

.mat-form-field.mat-focused.mat-accent .step-up-arrow,
.mat-form-field.mat-focused.mat-accent .step-down-arrow {
    color: mat-color($accent);
}

.mat-form-field.mat-form-field-invalid .step-up-arrow,
.mat-form-field.mat-form-field-invalid .step-down-arrow {
    color: mat-color($warn) !important;
}

.mat-form-field.mat-form-field-disabled .step-up-arrow,
.mat-form-field.mat-form-field-disabled .step-down-arrow {
    cursor: default;
    color: $disabled;
}

Typescript:
// try calling stepUp() on the input element (Chrome, Firefox, Safari)
// on failure, mimic the effect of stepUp() (Internet Explorer, Edge)
// return immediately if input is disabled
stepUp(input:HTMLInputElement) : void {
  if (input.disabled) {
    return;
  }
  try {
    input.stepUp();
  }
  catch (ex) {
    // increment `value` by `step` (default to '1' if `step` is absent)
    input.value = String(Number(input.value) + Number(input.step || '1'));
    // if `max` is present and `value` is greater than `max`, set `value` to `max`
    if (input.max && Number(input.value) > Number(input.max)) {
      input.value = input.max;
    }
  }
}

// try calling stepDown() on the input element (Chrome, Firefox, Safari)
// on failure, mimic the effect of stepDown() (Internet Explorer, Edge)
// return immediately if input is disabled
stepDown(input:HTMLInputElement) : void {
  if (input.disabled) {
    return;
  }
  try {
    input.stepDown();
  }
  catch (ex) {
    // decrement `value` by `step` (default to '1' if `step` is absent)
    input.value = String(Number(input.value) - Number(input.step || '1'));
    // if `min` is present and `value` is less than `min`, set `value` to `min`
    if (input.min && Number(input.value) < Number(input.min)) {
      input.value = input.min;
    }
  }
}

The result of this stackblitz:

What is the use-case or motivation for changing an existing behavior?
The arrows for stepping up and stepping down should be styled consistently with the arrow used in mat-selects and should work on all major browsers.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I tested this mock-up on Firefox, Chrome, IE 11, Edge, and Safari.
Is there anything else we should know?
This SCSS rule:
::ng-deep .step-arrow-wrapper + .mat-form-field-label-wrapper {
    width: calc(100% - 18px);
}

doesn't work in the stackblitz, but it works otherwise. Its purpose is to reduce the width of the mat-label so that a long label doesn't overlap the new step buttons.
Lastly, in Firefox, a "number" input with "textfield" appearance that is also disabled will allow you to click on the textbox or tab into it and edit it, even though it is disabled. This is a Firefox bug. To prevent clicking, set its pointer-events to none. To prevent tabbing, somewhat manually set the tabindex to -1:
[tabindex]="someQuantityInput.disabled ? -1 : 0"

I updated my examples to color the arrows correctly whether the input is active, inactive, invalid, or disabled, as well as correctly disable the arrows while the input is disabled.

This seems like we'd be polyfilling the native number inputs. The intention with matInput is only to style it like a Material Design input, with as little intervention as possible.

I respect your philosophy towards the role/responsibility of Material, and I'll be honest, I don't really understand the relationship between Material Design and Material.
However, given how bad the native number input handling is/how bad it looks, I think little intervention is a bad thing. From my point of view, this feels like a prime example of something Material should unify.
Feel free to close this issue. At the very least, hopefully other people who are dissatisfied with number inputs will stumble upon this issue and find my code helpful.

I see your point and I appreciate the detailed workaround, but the problem is that if we decided to do this for type="number", we'd have to start doing it for every single other type of input (datetime, color, text etc.`).

It is mid of 2022 and nothing is done regarding number input. I think it is a shame, that Angular team leaves such basic things as "non important". After all people are using Angular Material because of well done GUI. And you dont want to provide usable basic features. Even when somebody did the whole development and gave you a code. LOL, what? Product owner felt asleep behind the wheel.
It is the same story as with FormControl that does not support remembering of the original value and so every programmer has to re-implement this feature again and again. Somebody in Angular said: we dont think it is important to be able to reset to the original value. LOL and tears once again.
Thx @dannye. You saved me probably a day of work.


Updated XSD based on examples and reformatted examples to pass XML va…

…lidation

Closing this PR as I don't have permissions to resolve conflicts in the contributor's local branch. I will create a new PR in windows-docs-pr repo to merge these changes to master.


.travis.yaml: notifications to upstream

This disables sending travis notifications to upstream.

Sorry for not answering before (and for the few notifications), we saw your PR and will of course remove the link that push into your mailing lists

No worries!


Use gosu to install plugin as kibana user

Hi Jeffery, thanks for this - it looks like a nice optimisation. I'll merge and push that up now :)


Error when items quantity are changed

I know that Foundry v12 is not yet supported but I thought you might want to track.

Foundry v12.331
D&D5e v3.3.1
D&D5e Character Monitor v2.0.3

Also having the same issue. Also to double check version 2.0.2 says it was updated for v12 and D&D 5e version 3.3.1. Was curious if that was correct? Thanks in advance.

this should be fixed in the next update


Recommended changes resulting from automated audit

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.
We encourage you to make the following modifications:

[x] You are currently referencing Cake.Core 0.26.1. Please upgrade to 0.28.0
[x] Your addin should target netstandard2.0. Please note that there is no need to multi-target, netstandard2.0 is sufficient.
[ ] The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.rawgit.com/cake-contrib/graphics/a5cf0f881c390650144b2243ae551d5b9f836196/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.org and in the project on github.

After examining the project believe these suggestions have been implemented already. Please correct me if wrong.
Maybe close this issue?

@glBeatriz I have just merged your PR.  Your changes should go out with the next release.  Thank you!


Build fails to copy all required linux shared objects for TensorFlow version 1.15.

Describe the bug
Build fails to copy all required linux shared objects for TensorFlow version 1.15, TensorFlowSharp version 1.15.1.
To Reproduce
Run using TensorFlowSharp 1.15.1 NuGet packages on linux.
Expected behavior
Required dependencies to be available.
Exception
Unhandled Exception: System.DllNotFoundException: Unable to load shared library 'libtensorflow' or one of its dependencies.
Desktop (please complete the following information):
Debian GNU/Linux 9 (stretch) within Docker container.
Additional context
Only libtensorflow.so and libtensorflow_framework.so are copied from libtensorflow\lib to runtimes\linux\native\ as part of the build specified in TensorFlowSharp.csproj. The following additional libraries from libtensorflow are also required for running TensorFlow 1.15 on linux:
libtensorflow.so.1
libtensorflow.so.1.15.0
libtensorflow_framework.so.1
libtensorflow_framework.so.1.15.0

I suspect the same issue exists for the .dylib files required by OS X, though have not tested this myself.
I propose replacing the following lines in TensorFlowSharp.csproj:
<None Include="..\native\libtensorflow.so" Link="nuget\runtimes\linux\native\libtensorflow.so" PackagePath="runtimes\linux\native\libtensorflow.so" Pack="true" />
<None Include="..\native\libtensorflow_framework.so" Link="nuget\runtimes\linux\native\libtensorflow_framework.so" PackagePath="runtimes\linux\native\libtensorflow_framework.so" Pack="true" />

With the following:
<None Include="..\native\libtensorflow*.so*">
  <Link>nuget\runtimes\linux\native\%(Filename)%(Extension)</Link>
  <PackagePath>runtimes\linux\native\%(Filename)%(Extension)</PackagePath>
  <Pack>True</Pack>
</None>

Libtensorflow binaries
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-linux-x86_64-1.15.0.tar.gz
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-darwin-x86_64-1.15.0.tar.gz
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-1.15.0.zip
Please let me know if you'd like me to create a pull request to resolve this issue.

Hi @craigwalton,
I'm facing the same issue as you. In the meantime, I've created my own NuGet which is working. But it is not productized. It seems this project is not maintained anymore. How did you overcome the issue on your side ? Did you fork the project ? Did you create a new NuGet as well ? If yes, did you publish it in public repo ?
Thanks.

Hi @nateagr,
I am using TensorFlowSharp within a Docker container. So I added a RUN instruction to the Dockerfile which downloads (https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-linux-x86_64-1.15.0.tar.gz) and unpacks the missing libraries into the required directory. I did not fork the project or publish anything on NuGet.
Sorry - this probably is not much help to you.

Thanks for your answer 👍


[UT] UtFramework support shared-data cluster (1/3)

FE ut framework support creating a shared-data cluster

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[X] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[X] 3.2
[X] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio backport branch-3.2

@mergifyio backport branch-3.1


[PE-D][Tester E] Matching process is not explained well in UG

As a user, I want to make sure all matches are found, but if the matching process is not clear, I cannot verify that the app works as I expect.

Labels: severity.Low type.DocumentationBug
original: jerremyng/ped#9

DONE


[UpdatePlugin] Martin Petran (Martyx00) VulnFanatic v2.0

Please update my plugin:
Author: Martin Petran
Repo name: VulnFanatic
Release: https://github.com/Martyx00/VulnFanatic/releases/tag/v2.0

Closed as I need to do one small change :) Will submit the request later :)


Replace webpacker

Webpack is super slow and webpacker adds an additional level of indirection on top of Webpack’s own configuration.
Rails 7 will provide a thin integration layer for JS and CSS bundling tools as a replacement for webpacker. This layer handles only a few basic tasks, e.g. providing view helpers to include CSS and JS assets. Configuration of the actual build process etc. is completely up to the respective build tools, i.e. no more additional complexity.
Using the new tooling already works with Rails 6. This PR completely removes webpacker and replaces it with PostCSS CLI for CSS and esbuild for JS.

@tillprochaska feel free to merge


[AutoRelease] t2-eventgrid-2022-08-18-85822(Do not merge)

https://github.com/Azure/sdk-release-request/issues/3095
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=993
BuildTargetingString
azure-mgmt-eventgrid
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3095


Polymer 0.8 cant bind to array item.

This we could do in 5.x
Using an array property/attribute which is populated with an 'associative' array of values, There is an error on the bind..
Eg.
Setup and element with a property (we are using this for translating the page)
  translations:{
          value: [],
          type: Array,
          notify: true,
          readOnly: true
        },

populate translations with an array of Objects. eg.
var trans = [];
trans['id-one'] = 'one';
trans['id-two'] = 'two';
this._setTranslations(trans);

Then
use the element.
    <translator-json translations="{{translations}}" ></translator-json>
    <paper-button raised="true">[[translations['id-one']]]</paper-button>
    <paper-button raised="true">[[translations['id-two']]]</paper-button>

Results in an error in bind.html
unexpectedIdentifier
it creates a setter
"var old = this._setData('translations['id-one']', value);
if (value !== old) {
  this._translations['id-one']Effector(old);
}"

We do not plan to support [...] bracket dereferencing in 0.8+, as we are avoiding use of a full JS expression parser for performance and simplicity.
However, this syntax will work: [[translations.id-one]].


Add guidelines for contributing to the repo

Related to https://github.com/trailofbits/osquery-issues/issues/97

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[GLUTEN-7886][VL] Fix broken Ubuntu 20.04 + VCPKG + GCS + ABFS build

Fixes #7886
Reason:
set(CMAKE_FIND_LIBRARY_SUFFIXES ".so") in find_gcssdk affects find_azure unexpectedly.
Add push / pop logic against CMake var CMAKE_FIND_LIBRARY_SUFFIXES to prevent the local changes from escaping their scopes.
Tested locally.

@PHILO-HE Thanks

Nothing abnormal in CI build log, merging in advance.


MD-4312: Push Project past Correlate

Additional fixes for ProjectCorrelateTransposeRule

Code changes look good to me. +1


Set stewart-yu to emeritus approver

This PR removes @stewart-yu as an approver for k/website.
@stewart-yu missed his PR wrangler shift last week and doesn't have a Kubernetes Slack ID or clearly associated email to respond to queries. We haven't been able to reach him in over a week.
@stewart-yu We hope you're OK! 💜 Please let us know if you're on vacation or need a break. Also, please sign up for K8s slack and let a SIG Docs chair (myself, @jimangel, @Bradamant3) know how to contact you by email.
Update (15 Oct 2019)
@stewart-yu reached out to me on Slack (@Yu Chianjian) to provide his email address to let me know that he's busy with work and will be returning in a month's time.
I recommend we assign him status as an emeritus approver (no ability to approve PRs, no auto assignments, can return later at their discretion).
Lazy consensus
This PR should merge unless these three conditions are true by 5:30pm Pacific on Thursday, October 10, 2019 (~48 hours from now):

[ ] @stewart-yu replies to this PR
[x] @stewart-yu signs up for Kubernetes Slack
[x] @stewart-yu shares an email address with at least one chair of SIG Docs via Slack

Dependency
If this PR merges, it requires a followup PR in k/org.
/assign @Bradamant3 @jimangel

Reply in slack

/lgtm

/lgtm

/approve


How to visualize the segmentation results on the Semantic3D dataset?

Hi,How do I visualize the segmentation results on the Semantic3D dataset?

Same as S3DIS, some .ply file are saved in the log folder. Just search for them in the folder called val_preds
I don't save all the frames as .ply because it would be too big. Only one frame every 20 frames is saved or something.


OrderBillingAddress column removed from order table

Story AB#9714
Task AB#7941
OrderBillingAddress column removed from order table

Your changes look good. However, before I approve can you squash your commits and reword your commit message?
 Therefore, I'd recommend rewording your commit message to something like: 'Remove OrderBillingAddressId column from Order table'

I have updated Commit message.

Your changes look good. However, before I approve can you squash your commits and reword your commit message?
 Therefore, I'd recommend rewording your commit message to something like: 'Remove OrderBillingAddressId column from Order table'

reopening the pull request, closed accidently

Approved. Select squash and merge to squash your commits down to one.


Add table aws_wafv2_ip_set

References
Add any related links that will help us understand the resource, including vendor documentation, related GitHub issues, and Go SDK documentation.
<EMAIL_ADDRESS>

Duplicate :https://github.com/turbot/steampipe-plugin-aws/issues/250


Not able to find footer code

Hello,
This is my first time theming for Shopify theme so forgive me if I ask really simple question. I am trying to edit the code for footer in this theme. As footer is a section, I am editing /src/section/footer.liquid but my change doesn't appear on the page.
Am I editing wrong file?
Here is the link: https://dhaval-demo-3.myshopify.com/
Password: demo3-dhaval
Best,
Dhaval

So, I realized that there was a different code in /src/section/footer.liquid file than what I had locally. I tried to use Theme download command but it didn't work. So, I manually copied file locally and then updated my code and then ran npm run deploy and it worked. It pushed my changes to the store site.
If this is not the correct way to do it or if there is a better way to do it, please let me know.
Thanks.

👋 first question, when developing, are you running yarn start without any errors in the terminal?

Hey 👋 I am using npm run start and yes, it runs without any errors.

If you npm run start and save your footer.liquid file, in your terminal you should see it being uploaded to your Shopify store. You would only need to refresh the page to see the changes.

Unfortunately, that wasn't the case. I was running start command and then I made some changes in my file. But it never updates it on the site. I had to copy code from "Theme Editor" from "Admin" screen and paste it locally to Footer.liquid file and then make changes into it get it working. Not sure if I am doing anything wrong.

What do you see in your terminal when you update a liquid file?

Sorry for the delayed response on this. Happy New year btw. I think I resolved the issue. I don't have all the files on my local workspace so I would have to download those files and then upload it to get it working. Everything is working fine now and thanks for your help. :)


Fixes for issues found when adding ODD integration tests to .NET SDK

Description
Fixes for issues found when adding ODD integration tests to .NET SDK
Tests are failing at this point, will need to fix those in subsequent commits..

@artur-ciocanu I've reverted onDeviceAllMatchingRulesMboxes removal, please take another look, thx!