bazel 3.0.0
running with scissors
built and deployed node, pool, channel node of latest master and deployed, seems fine so far
and can you please get rid of this on the client init? :smile: ```SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.```
and not by hiding it, either explicitly defining to use the NOP logger or including that implementation it tries to use in the build
and i'll report tomorrow if you fixed something between `a20502254b677d1fe8d1f72f9577e4b6af3a9803` and `181e36f37aeee0e58cbb49cec10bf09e836ad29c` in regards to the memory use, but i'll not bother bisecting
and channels is now off `a1c5ad606c419878275cdbe195fd8b8f52338800`, did not bother noting down what it was off before, as it's been fine so far
Apr 08, 2020 10:44:29 AM duckutil.PeriodicThread run WARNING: Periodic thread exception snowblossom.lib.db.DBTooManyResultsException at snowblossom.lib.db.rocksdb.RocksDBMap.getByPrefix(RocksDBMap.java:162) at snowblossom.channels.ChunkMapUtils.getWantList(ChunkMapUtils.java:118) at snowblossom.channels.ChannelChunkGetter.startPulls(ChannelChunkGetter.java:136) at snowblossom.channels.ChannelChunkGetter.runPass(ChannelChunkGetter.java:102) at duckutil.PeriodicThread.run(PeriodicThread.java:30)
[snowblossomcoin/channels] Issue closed by fireduck64