Repository navigation
Fix #758: Memmy 概览页面持续提示“memory layer network error”,重启后仍无法恢复 - #760
Open
Memtensor-AI wants to merge 1 commit into
Open
Memtensor-AI wants to merge 1 commit into
Memtensor-AI wants to merge 1 commit into
Conversation
The overview panel treated a single failed read as a terminal state: it replaced any cached snapshot with the raw "memory layer network error" text, had no retry, and offered no way out. When the local Memory service was still installing, migrating, or wedged, the page stayed broken until it remounted — including across app restarts, which is the reported symptom. Load panel data through a shared useMemoryPanelLoad hook that keeps the last good snapshot on screen, retries on a backoff schedule, and surfaces an actionable notice with retry and service-restart actions once automatic attempts run out. Apply it to both the overview and analytics panels, which read the same service and previously dead-ended the same way. The raw backend message is kept, but demoted to a diagnostic line with the request id; users now see what failed and what to do about it. Refs MemTensor#758
This branch has not been deployed
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.
Description
Fixed the persistent "memory layer network error" on the Memory overview page.
Root cause: OverviewSubPage treated a single failed panel read as terminal. It replaced any cached snapshot with the raw backend text ("memory layer network error"), had no retry, and offered no recovery action. The Memory service runs as a local child process that is briefly unreachable while installing, migrating, or restarting; the backend maps that to memory_layer_unavailable (503), so one unlucky read left the page permanently broken until it remounted — matching the reported "still broken after restarting the app" behavior.
Changes (App/frontend/desktop):
Verification:
Commit daeab8f on feature/autodev-758-20261027084326546, pushed to remote.
Related Issue (Required): Fixes #758
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Automated tests are pending.
Checklist
Reviewer Checklist