Stéphane Duchesneau

do you see an improvement if you do the same query again ?

It's usually when a subscriber (incoming connection) does not read data fast enough, so instead of accumulating tons and tons of data in a buffer and going to OOMkill, it...

Proposed simplified implementation (no hash optimization, no proto changes) 1. when a new filter is applied for any type (include, exclude, ...), if a filter is already present, the new...

[races-log.txt](https://github.com/dfuse-io/dfuse-eosio/files/4653021/races-log.txt)

I'm OK with proposed procedure (the last successfully loaded block could even be flushed every 100 blocks or whatever. `Another possibility would be to look up the highest block_number from...

Cannot reproduce. * Go repository has no report of other issues with this (not after 2018) * Issue appeared on reading from a channel (which should be a thread-safe operation)...

note: pr #47 is now merged into develop

tokenmeta and search-live expose health grpc status here's what I get from running dfuseeos with all default settings on a producing chain: ``` #live-search on port 13017 grpcurl -v -plaintext...

https://docs.dfuse.io/eosio/admin-guide/monitoring/

eosc tx unpack mytx.json --skip-sign panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x8a3334] ```goroutine 1 [running]: github.com/eoscanada/eosc/eosc/cmd.glob..func55(0xe06c80, 0xc42012ee60, 0x1, 0x2) /home/stepd/go/src/github.com/eoscanada/eosc/eosc/cmd/txUnpack.go:30...