Repository navigation
Fix data recovery, offline packaging, and async reliability - #11
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.
Interrupted personal-data restores and map activations could leave partially replaced data or mixed file versions. Offline kits omitted required rebuild inputs, while GPX imports and delayed frontend responses could retain partial or obsolete results. This change addresses the 14 reliability findings and adds regression coverage for their failure paths.
docs/RELIABILITY_FIXES.mdanddocs/RELIABILITY_FIXES.zh-CN.md.Validation: the complete local
staticprofile passed in 37.1 seconds, including 15 frontend cases, 52 offline-kit assertions, 4 offline-map scenarios, and 16 operation failure/recovery scenarios. Python regressions andgit diff --checkpassed. GitHub Actions passed on Windows and Ubuntu, including the dedicated real PostGIS distance, nearby-query and migration checks that were skipped locally because Docker is unavailable. Browser/full/offline recovery drills require the real service stack and have not been run.Deployment: migration
008_geography_distances.sqlrecalculates existing track lengths and uses the existing version/history triggers. The migration, production service rebuilds, and large offline-kit refreshes have not been applied to personal data by this change.