[snowblossomcoin/snowblossom] #88 adding pool failover to pool miner
well, there is pool miner failover. It's probably not ideal because it won't try and occassionally try to get back on your preferred pool, but it works.
@Clueless just gnu coreutils
bah, stupid behavior with precache where it will always connect to the second host because it will always hit the case of looking like it was stalled.
also thought up a better examples of localization: if a culture expects a different introduction order of things for logic to hold water, the order of wizard pages will have to be shuffled and the contents reworked what they do to television program formats when they do a local version of something
@Tyler Boone i like that change as it makes this a stability competition between the pools
haha. yeah if a lot of people have that set up then if you restart your pool you will lose a lot of miners
not really the behavior I want though...
work on a feature branch for stuff like that so it’ll not end up in production if an emergency release needs to get cut
I pretty much always use branches
fireduck is the "party in master" dude
Alright, I'm off to bed. wife's getting impatient.
ttyl sir
oh that was a pr, read it as a commit note as a lot of things are
party in master 24x7
google got me in that habit
I can't understand how a company that large works with that many people just checking into master but somehow it does
staggered a|b testing style deployment and everyone is liable? (pure guess)
heavy reliance of pre-checking automation
to do builds and run tests
obviously someone there was very good at both building processes and pressing people into the mould
tough stuff, designing for the human element
it still seems weird to me. how can a developer work on 2 things at once?
I mean... it's throwing away the single biggest advantage of git
many ways to rome
also the company is older than git
doesn't mean they don't use it.
Microsoft is too, but git is now the most prevalent repo
but actually yeah you are right. if they aren't on git, it makes total sense
They are on g4 which is a rewrite of perforce
Devs do two things at once by having multiple checkouts in these citc things. Client in the cloud.
Some do use branches
Or a git proxy thing
It worked very well. I spent most of my time fighting people not tech.
that's fine. They did an internal implementation that gave them the same thing as git branches
so it's actually like they were using pull requests :slightly_smiling_face:
Yeah. You could clone or run someone's citc client to check it
i was pointing out their legacy for their workflow predates the modern hot thing and big ships turn slow, and whatever they do seems to be working out ok for them
@Tyler Boone or I can be a dick and have two pools prepared. `http://snowday.fun` and not lose any
Add ability to split the main snow field file into chunks and put them on separate media. This will allow people to: 1. put some stuff in memory filesystems 2. use storage that doesn't quite fit (example, 256gb field on 250gb ssd) etc. If we do this nicely, we allow a ton of flexibility without having to special case it all in the miner.
nice, the git integration edits the post
yeah, I love it
@Fireduck can you connect the discord thing? People would like to see it.
@Clueless that’d just be being well prepared rather than a dick, IMO
@Rotonen Kindergarten once told me I should share.
yeah, when I ran HHTT I had three endpoints up
I'm playing around with their "floating ips" I should be able to push people onto a different VM before spinning this one down.
So a work unit sent to a miner only has any meaning to the mrplow that issued it
it is basically an ID number
which has to be matched up to the rest of the block header and block that it relates to
so currently, nice active-active setup isn't really possible
I figured, so it'll interrupt the miner slightly, but it shouldn't fail over.
in this case, it's a manual switch
/poll "Continue to maintain SnowBlossomMiner with feature parity to PoolMiner?" "Yes" "No"
Open Slack to cast your vote in this Simple Poll Open Slack to cast your vote in this Simple Poll Open Slack to cast your vote in this Simple Poll
Is there any difficulty in maintaining feature parity?
Is there a way you can make Miner extensible?
A little, we are going to be adding new features for things like failover, reading from multiple locations
Then when a common feature comes out, you only put it in Miner, but PoolMiner inherits it
and other improvements
Yeah, they work differently enough that it would be difficult.
One deals with work units, the other with whole blocks
doable, but maybe not worth it
If someone wants to solo mine, they can always spin up a plow and point a pool miner at it
seems reasonable to me.
@Clueless, having a backup pool isn't a "dick move", it's totes legit. just convince your users they should put those first
That way the java code can do the headers and proof work while allowing other binary mining programs.
l assume the pool_host config value survive spaces `pool_host=http://snowday.fun`
you make funny assumptions
adjust your algorithm to "assume dumbest thing"
I am using some sort of java properties parser
I don't actually know what it does
well, I'll test it
just firewall connections out to pool1, and see if the poolminer connects to pool2
i’d not even assume it survives non-punycode i18n domains