Repository navigation
Fix Network loading while QDN data downloads in Hub and Home - #41
Merged
Merged
Conversation
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
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.
Qortal Hub can load Network before its node has downloaded the DATABASE payload. Hub's default public node reproduced this with 4 of 7 chunks and Core error 1401 (
Data unavailable). Network immediately fell back to sample data and rendered the rejected error object as[object Object].Network 1.4.5 now requests the database's resource status with
build: true, shows download progress, and waits forREADYbefore reading the index or snapshot. The wait is capped at 90 seconds, including a host request that never settles; navigation or a new load cancels it. Unavailable/blocked/error outcomes have readable messages and a Refresh/node-choice hint. Historical-load failures correctly label the previously displayed snapshot. Both QDN builds retain their existing data identities and Developers visibility.Validation: 99 tests pass, including the observed Hub error envelope, download/build/READY transitions, timeout, cancellation, malformed status, and both bridge selections. TypeScript and both production builds pass. Actual Hub 3.0.3 testing uses its Core-injected lexical bridge and real data from ext-node.qortal.link; the node reached 7/7 chunks and the candidate displayed 63 nodes/221 links, historical records, and hidden Developers aliases through Back/Forward. Home desktop checks pass on Qortium and Qortal. Physical Android checks also pass on both networks, including medium/huge text, Classic/Modern, light/dark layout, history, and Developers visibility. All five GitHub checks are green at
419dcff.Desktop candidate testing substitutes only Network JS/CSS. Android uses read-only candidate asset routes with the native Home bridge and actual Qortium/Qortal DATABASE reads. Host bridges and data remain real. Unmodified published 1.4.4 also passed Hub startup after its default node completed the download, confirming availability as the trigger. Home tests include the already-merged #550 compatibility fix. No Home release, publisher change, data publication or Network 1.4.5 publication is included in this PR.
Release completion (2026-09-09): merged as
a8f54dcadc02d5f5fa5ae8f608d4e2b3c2c75737after owner approval and green checks. Network1.4.5 is published as Qortium APP/Network/Network and Qortal APP/xnetwork/default. Both merged-main builds match the tested candidate exactly. All eight files match on the local node, both Qortium seeds, and Qortal appnode/ext-node. Actual published Hub3.0.3 plus Home desktop/physical Android checks pass for data/history/Developers visibility; the phone layout matrix also passes. Qortal publication confirmed in block2718201 with a0.01QORT fee. No Home binary or DATABASE/publisher update was needed for this app-only release. This supersedes the candidate/publication boundary described above.