[snowblossomcoin/channels] Issue opened by fireduck64
[snowblossomcoin/channels] Issue closed by fireduck64
you have a lot more build time bazel noise
yes
they have decided that sha1 isn't cool any more
and it is somewhat tedious to move over to sha256 for each package
it should only be noisy on one run
i only ever do nuke from orbit clean builds
ha, good
so now the node wants to reindex the whole blockchain?
there is a weird pattern of burst of 30k and stall, burst of 30k and stall
though that's probably disk limited
it might be the blocks that were actually full in load testing
yeah, it is rebuilding the transaction and address history indexes using my hashed trie data structure
the same code as the utxo structure
did you cock up the networking? ```Nov 22, 2019 7:17:38 PM snowblossom.node.SnowUserService sendNewBlocks INFO: Error: io.grpc.StatusRuntimeException: CANCELLED: call already cancelled```
I don't think so
it's doing that roughly every 30s
Is it connected to a mining pool?
yep
hum
only a pool is connected to it
and no one is connected to the pool
yeah, it is absolutely doing that
I wonder why....but I don't think it is new
or a problem
i jumped from some 1.5.x
I'll take a look in a bit
log spam is annoying, though
agreed
I can't figure out a reason that streaming request would ever be closed
oh, nevermind, MrPlow is making a new channel each time for some reason
nothing weird in the pool logs
yay a bug
I should switch it to my new stub management anyways
git blame yourself for the root, though
always good to self educate
ha
node logs have a lot of: Nov 22, 2019 7:17:38 PM snowblossom.node.SnowUserService sendNewBlocks INFO: Error: io.grpc.StatusRuntimeException: CANCELLED: call already cancelled Mr plow is making a new connection every 20 seconds or so. It should use the existing one as long as we are still getting block templates.
[snowblossomcoin/snowblossom] Issue closed by fireduck64
Good
what's `logger.fine` ?
a log level that doesn't print on normal settings
so the fix was to not break the connections and not log that anyways
since we don't really care
i did not update my node, so you actually also fixed something