[fit] Re-register all information to the registry after successful reconnection#149
Merged
CodeCasterX merged 1 commit into3.5.xfrom May 30, 2025
Merged
[fit] Re-register all information to the registry after successful reconnection#149CodeCasterX merged 1 commit into3.5.xfrom
CodeCasterX merged 1 commit into3.5.xfrom
Conversation
…re-register all information to the registration center
CodeCasterX
approved these changes
May 30, 2025
Yager-42
pushed a commit
to Yager-42/fit-framework
that referenced
this pull request
Aug 16, 2025
…re-register all information to the registration center (ModelEngine-Group#149)
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.
The current logic is that after the heartbeat goes offline, the information is not successfully re-registered to the registration center, resulting in a no fitables exception error in the request.