docs(gateway): add process isolation troubleshooting#215
Open
RerankerGuo wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ziyang Guo <121015044+RerankerGuo@users.noreply.github.com>
Collaborator
|
Thanks for your attention. We will review it and get back to you soon. |
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
2 participants
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 | 描述
Add README troubleshooting steps for unexpected
/recalldata that appears to come from another user.The new note tells operators to verify which Gateway process owns port
8420, inspect itscwd,HOME,USER,TDAI_DATA_DIR, and open memory-tencentdb files, then distinguish a real isolation problem from hitting an older or different sidecar process.This is documentation-only and does not change runtime behavior.
Related Issue | 关联 Issue
Related to #62
Change Type | 修改类型
Self-test Checklist | 自测清单
Additional Notes | 其他说明
Verified with
npm testandnpm run buildusing Node v24.15.0.