bugfix: fix internalserverError while connecting mongoDB with clustering uri #20
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.
🔍 What type of PR is this?
bug
👀 What this PR does / why we need it:
🅰 Which issue(s) this PR fixes:
Fixes openimsdk/open-im-server#1627
📝 Special notes for your reviewer:
root cause: context management in Golang.
In the m.tx code block within the initialization function, misusing the ctx parameter as the parameter for end session and Transaction function calls actually captures a context that does not exist in the init function. Therefore, it causes the first user registration to succeed in a clustering architecture (because at this point the ctx is the same as the actual execution context of the function). However, the second execution fails (since the ctx within m.tx is garbage-collected at the end of the first task).
🎯 Describe how to verify it
📑 Additional documentation e.g., RFC, notion, Google docs, usage docs, etc.: