Ensure unique connection storage per session#2724
Merged
Merged
Conversation
Signed-off-by: worksofliam <mrliamallan@live.co.uk>
worksofliam
had a problem deploying
to
testing_environment
June 11, 2025 14:10 — with
GitHub Actions
Failure
Contributor
|
👋 A new build is available for this PR based on 70321fd. |
sebjulliand
approved these changes
Jun 11, 2025
sebjulliand
left a comment
Member
There was a problem hiding this comment.
Good job @worksofliam , that fixed it 😄
Merge away!
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.
Implement a mechanism to set a unique key prefix for connection storage, ensuring that each connection maintains its own distinct storage context. This change enhances the organization and retrieval of connection-specific data.