Reset DataTypeTree and DataTypeManager on Session initialization#1711
Merged
kevinherron merged 1 commit intomainfrom Mar 28, 2026
Merged
Reset DataTypeTree and DataTypeManager on Session initialization#1711kevinherron merged 1 commit intomainfrom
kevinherron merged 1 commit intomainfrom
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
1 participant
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.
Reset the DataTypeTree, dynamic DataTypeManager, and dynamic EncodingContext automatically when a new session is initialized.
These caches are lazily populated by browsing and reading from the connected server. When a client reconnects — whether by creating a new session or reactivating an existing one — the server's type system may no longer match what was cached. Custom DataTypes may have been added, removed, or modified, DataTypeDefinition attributes may have changed, namespace indices may have shifted, or the client may have reconnected to an entirely different server in a redundancy configuration.