that multiple builds behaviour is curious
i’d guess either the webhooks are set up weird on github or the config on dockerhub is wonky
cannot really take a look as i have no visibility into either
Right, and the docker bazel builds are super slow because they need to download the world
those being slow are not an actual issue
sure, except dockerhub seems to assign us one or two build slots
so things take some time when I wildly push commits
it’s semi amazing they do even that for free
they have a virtual lock on that market, costs to keep that
1.8.0 - Advent of Blocks New in this release, we are now building a Windows installer that includes OpenJDK. That is the .MSI file and is super easy to run in Windows. https://snowblossom.org/releases/index.html • SIP4 - Input value checking set for block 151680 • Update seed nodes • Add remote address to Shackleton explorer logs • Switch Shackleton web handling over to new web framework • Added explorer APIs zone and /api/total_coins • Lower max history replies • Add get_address_history rpc • Fixed presentation bug in unspent with mempool • Added public note string to iceleaf send panel
they probably spend more money letting the world download docker images
the building is probably a small fraction
does that msi already handle the case of a preexisting installation
Yep. Just replaces if version number is higher.
good, IIRC there was some weird hiccup with the installers earlier in regards to that
Yeah, I had to do some things to make an increasing version number.
If you dig in, that msi is actually 1.8.1009 or something
so rolling build number, gotcha
And my next build would be 1.8.1010
Yeah