Skip to content

196 refactor conversationid stacking#203

Open
biniyam-29 wants to merge 71 commits intorelease-02from
196-refactor-conversationid-stacking
Open

196 refactor conversationid stacking#203
biniyam-29 wants to merge 71 commits intorelease-02from
196-refactor-conversationid-stacking

Conversation

@biniyam-29
Copy link
Copy Markdown
Collaborator

@biniyam-29 biniyam-29 commented Apr 15, 2025

  • fixed what used to be a bottle-neck to the system
  • the mentor who is having the conversation used to be checked on the back-end (aka the system not in microservices), which caused a bottle-neck. this check was placed there so as to differentiate which messages has to be sent to the moderator.
  • change where the check occurs, which is in the message consumer-microservice. now the problem is solved.
  • also I've made some updates on other modules as well so as to go with the new refactoring. like the database consumer used to binded with the modrator routing as well but now it is not.

…etter-exchange' for queue 'database' in vhost '/': received 'moderator' but current is 'message'
…or-mentor-profile' into 175-converse-with-gemini-api-using-langchain
…e it was not getting and response from the consumer)
…was throwing error cause it is stringfied, so placed a parser based on type)
@biniyam-29 biniyam-29 linked an issue Apr 15, 2025 that may be closed by this pull request
@biniyam-29 biniyam-29 requested a review from bengeos April 15, 2025 15:22
@biniyam-29 biniyam-29 self-assigned this Apr 15, 2025
@biniyam-29 biniyam-29 added the enhancement New feature or request label Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

refactor conversationId stacking

2 participants