archive snowblossom slack dev
prev 2020-02-04 next
2020-02-04 09:59:38
Rotonen
the pool now has these in the logs ```Feb 04, 2020 9:56:16 AM snowblossom.miner.plow.MrPlow$BlockTemplateEater onError INFO: Got error:io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdownNow invoked```
2020-02-04 10:00:24
Rotonen
it is getting the block info too, but something is erroring out
2020-02-04 16:26:15
Fireduck
Yeah, it is messily creating new connections
2020-02-04 16:26:36
Fireduck
Which is what I was trying to fix when I introduced that bug
2020-02-04 21:13:51
Rotonen
frying pan -> fire
2020-02-04 21:14:35
Fireduck
yeah, so I did a simple revert of that
2020-02-04 21:14:39
Fireduck
working on a better fix now
2020-02-04 21:15:29
Rotonen
i can do low impact testing as essentially no one mines on my pool
2020-02-04 21:16:36
Fireduck
it took me stupidly long to get my unit test for this case working
2020-02-04 21:17:05
Fireduck
turns out I was running the MrPlow maintenance loop from main() so my tests were not running it at all
2020-02-04 21:37:13
Rotonen
rough
2020-02-04 21:38:12
Rotonen
i suppose it’d not be too fun to blackbox / smoketest that with controlling processes and asserting on the log output?
2020-02-04 21:38:54
Rotonen
mostly the data setup would be hard to build and still not make it realistic
2020-02-04 21:40:01
Rotonen
hmm, maybe build a log parser with a whitelist and have it alert you of every unexpected output? and just leave stuff running?
2020-02-04 21:40:02
Fireduck
For most of my modules, it is easy to start them up with just new Thing(config)
2020-02-04 21:40:17
Fireduck
and then I can use methods on the thing to check on its state
2020-02-04 21:40:35
Fireduck
so in the case of the mining test, I start up a node, a MrPlow and two miners
2020-02-04 21:40:47
Fireduck
then I check with a client connected to the node that the miners are making funds
2020-02-04 21:41:23
Rotonen
that’s already better orchestrated than i’m assuming
2020-02-04 21:41:42
Fireduck
then I call the shutdown methods, which may or may not work
2020-02-04 21:41:51
Fireduck
but regardless, junit/bazel cleans it up eventually
2020-02-04 21:42:14
Fireduck
There are almost certainly some linger thread pools and such, but not a big deal
2020-02-04 21:47:01
Fireduck
new version is looking good, but the node will need to be updated first
2020-02-04 21:47:08
Fireduck
There is a new updatable template grpc
2020-02-04 22:01:49
Fireduck
other than one of my testnet nodes was way out of date, it seems to be working fine
2020-02-04 22:06:25
Rotonen
does only the pool depend on the block template?
2020-02-04 22:07:37
Fireduck
The old solo miner does
2020-02-04 22:07:49
Fireduck
which is why I am leaving in the old rpc
2020-02-04 22:07:52
Fireduck
not a lot of code
2020-02-04 22:22:51
Rotonen
rather kill the solo miner than carry cruft?
2020-02-04 22:23:16
Rotonen
for anyone mad enough to think they can do it, they might as well go for writing their own miner instead
2020-02-04 22:25:03
Fireduck
The cruft is about 10 lines, I'm not worried about it
2020-02-04 22:26:56
Rotonen
so it starts
2020-02-04 22:27:05
Rotonen
removing code is like the best thing ever
2020-02-04 22:29:56
Fireduck
When I was at Amazon I did a project where I was about to delete a few packages totaling about 25k lines of stupid. That was good.
2020-02-04 22:31:09
Rotonen
i'd love to see the process red tape for that :smile:
2020-02-04 22:32:21
Fireduck
Basically none. The previous packages were a dumpster fire.
2020-02-04 22:32:38
Fireduck
My replacement worked faster, more reliably and with about half the hardware
2020-02-04 22:32:59
Fireduck
But this was a long time ago, probably 2010 or so
2020-02-04 22:33:13
Rotonen
maybe it's different when you're in house, as an external it was thicker than any governments i've dealt with in similar circumstances
2020-02-04 22:33:50
Rotonen
my experience is from 2014
2020-02-04 22:34:14
Fireduck
It was a relatively new cloud product at the time (SNS)
2020-02-04 22:35:03
Rotonen
used that in 2012 to pass turns around in a turn based iOS game
2020-02-04 22:35:17
Rotonen
the pricing model was prone for abusing the hell out of it
2020-02-04 22:35:38
Fireduck
good
2020-02-04 22:37:21
Fireduck
The parts I replaced had so much insane broker indirection that it sometimes delivered messages to the wrong queue (owned by a different customer)
2020-02-04 22:37:54
Rotonen
off by one? :smile:
2020-02-04 22:38:35
Fireduck
timing issue, grab a broken from a pool, assign it to an endpoint, use it
2020-02-04 22:38:46
Fireduck
something like that, but with some sort of really stupid race condition
2020-02-04 22:39:37
Rotonen
as a business with cash to burn in getting a position in a new market, it's not a bad idea to go live with something which is barely holding together
2020-02-04 22:39:53
Rotonen
if the business side of it makes any sense, then just burn more cash to redo it
2020-02-04 22:40:18
Fireduck
yeah, probably true
2020-02-04 22:40:19
Rotonen
there are not many companies on the planet where that makes sense
2020-02-04 22:40:29
Rotonen
but amazon certainly has the cash
2020-02-04 22:40:31
Fireduck
like how S3 implemented reduced redundancy storage at first
2020-02-04 22:40:49
Fireduck
Initially, it was just a bit you set that charged you less money
2020-02-04 22:41:14
Fireduck
And they would (I imagine) run a query occasionally to see how much they would save by implementing the actual feature
2020-02-04 22:41:32
Rotonen
yep
2020-02-04 22:42:11
Rotonen
also there's the classic category of not doing some expensive rarely used doohickey in tech, but actually dedicating people to act behind the curtain
2020-02-04 22:42:39
Fireduck
hah, yeah
2020-02-04 22:42:43
Rotonen
probably going to be better and more accurate than the initial implementation would be anyway :smile: