Release AxeDGB 0.9.180-dev with memory protection and offline setup - #44
Merged
Merged
Conversation
WillItMod
marked this pull request as ready for review
September 14, 2026 14:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release AxeDGB 0.9.180-dev with actual Core memory measurements, a configurable graceful memory guard, explicit resume after failures, and setup tools bundled into the init image. This removes the Alpine repository dependency that prevented fresh installations from creating Miningcore tables.
The update refreshes the persistent node launcher, retains Core 9.26.5 and existing chain data, reports setup failures, and creates a fresh schema in one transaction. The memory guard is a soft shutdown budget, not an instantaneous allocation cap or a reduction in Core's block-index footprint.
Validation: 33 application/API/supervisor tests and three packaging tests passed. Offline fresh initialization, real Core regtest restart/resume with three preserved blocks, a sustained-memory clean shutdown, and browser settings/resume behaviour were tested in isolation. The published images also passed the regtest API/memory smoke check and existing-database initialization.
All three images at 0.9.180-dev are published for amd64 and arm64 and were pulled without registry credentials:
Application change · Multiarch build
Keep the main channel unchanged until affected mainnet installations have been soak tested. This release does not require a blockchain purge or reindex.