archive snowblossom slack dev
prev 2019-11-22 next
2019-11-22 03:55:56
GitHub
[snowblossomcoin/channels] Issue opened by fireduck64
2019-11-22 05:14:15
GitHub
[snowblossomcoin/channels] Issue closed by fireduck64
2019-11-22 19:08:55
Rotonen
you have a lot more build time bazel noise
2019-11-22 19:09:53
Fireduck
yes
2019-11-22 19:10:01
Fireduck
they have decided that sha1 isn't cool any more
2019-11-22 19:10:15
Fireduck
and it is somewhat tedious to move over to sha256 for each package
2019-11-22 19:10:24
Fireduck
it should only be noisy on one run
2019-11-22 19:13:15
Rotonen
i only ever do nuke from orbit clean builds
2019-11-22 19:13:35
Fireduck
ha, good
2019-11-22 19:14:00
Rotonen
so now the node wants to reindex the whole blockchain?
2019-11-22 19:14:29
Rotonen
there is a weird pattern of burst of 30k and stall, burst of 30k and stall
2019-11-22 19:14:35
Rotonen
though that's probably disk limited
2019-11-22 19:15:35
Fireduck
it might be the blocks that were actually full in load testing
2019-11-22 19:15:55
Fireduck
yeah, it is rebuilding the transaction and address history indexes using my hashed trie data structure
2019-11-22 19:16:03
Fireduck
the same code as the utxo structure
2019-11-22 19:17:53
Rotonen
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```
2019-11-22 19:19:04
Fireduck
I don't think so
2019-11-22 19:19:25
Rotonen
it's doing that roughly every 30s
2019-11-22 19:19:41
Fireduck
Is it connected to a mining pool?
2019-11-22 19:19:46
Rotonen
yep
2019-11-22 19:19:49
Fireduck
hum
2019-11-22 19:20:12
Rotonen
only a pool is connected to it
2019-11-22 19:20:21
Rotonen
and no one is connected to the pool
2019-11-22 19:20:28
Fireduck
yeah, it is absolutely doing that
2019-11-22 19:20:34
Fireduck
I wonder why....but I don't think it is new
2019-11-22 19:20:40
Fireduck
or a problem
2019-11-22 19:20:51
Rotonen
i jumped from some 1.5.x
2019-11-22 19:21:01
Fireduck
I'll take a look in a bit
2019-11-22 19:21:03
Rotonen
log spam is annoying, though
2019-11-22 20:19:14
Fireduck
agreed
2019-11-22 20:24:31
Fireduck
I can't figure out a reason that streaming request would ever be closed
2019-11-22 20:26:33
Fireduck
oh, nevermind, MrPlow is making a new channel each time for some reason
2019-11-22 20:26:33
Rotonen
nothing weird in the pool logs
2019-11-22 20:26:40
Rotonen
yay a bug
2019-11-22 20:26:52
Fireduck
I should switch it to my new stub management anyways
2019-11-22 20:27:36
Rotonen
git blame yourself for the root, though
2019-11-22 20:27:40
Rotonen
always good to self educate
2019-11-22 20:27:53
Fireduck
ha
2019-11-22 20:44:26
GitHub
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.
2019-11-22 20:45:26
GitHub
[snowblossomcoin/snowblossom] Issue closed by fireduck64
2019-11-22 22:26:59
Fireduck
Good
2019-11-22 22:27:36
Rotonen
what's `logger.fine` ?
2019-11-22 22:28:54
Fireduck
a log level that doesn't print on normal settings
2019-11-22 22:29:21
Fireduck
so the fix was to not break the connections and not log that anyways
2019-11-22 22:29:24
Fireduck
since we don't really care
2019-11-22 22:52:48
Rotonen
i did not update my node, so you actually also fixed something