Skip to content

Fix data recovery, offline packaging, and async reliability - #11

Merged
bd4rex merged 1 commit into
mainfrom
codex/reliability-fixes-20260906
Sep 5, 2026
Merged

bd4rex merged 1 commit into
mainfrom
codex/reliability-fixes-20260906

Conversation

@bd4rex

@bd4rex bd4rex commented Sep 5, 2026 •

Copy link
Copy Markdown
Owner

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.

  • Make personal restore transactional with database/media safety checkpoints, service coordination, and retryable recovery even when recovery itself is interrupted. Validate complete map candidates before publishing and recover interrupted activations from durable journals and preserved snapshots.
  • Share offline project and immutable image inventories across creation, refresh, and verification. Include configuration and Linux entry points, reject inconsistent map snapshots, and distinguish complete project payloads from rebuild-ready kits.
  • Use standard newline-delimited MCP stdio, validate GPX files before one-transaction imports, calculate geography distances, and fix nearby-place queries with a matching spatial index.
  • Bind route results and saves to their input snapshot, reuse in-flight live-layer requests, clear empty map catalogs, start AIS on demand, and bound the response cache with TTL/LRU eviction.
  • Add isolated Python, Node, and PowerShell regressions, a disposable PostGIS CI job, and bilingual upgrade/recovery notes in docs/RELIABILITY_FIXES.md and docs/RELIABILITY_FIXES.zh-CN.md.

Validation: the complete local static profile 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 and git diff --check passed. 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.sql recalculates 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.

@bd4rex
bd4rex merged commit bce32a2 into main Sep 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant