-
Notifications
You must be signed in to change notification settings - Fork 26
Fix/speaker backend integration #133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
LGTM! Shared network enables cross-project service communication.
The
friend-networkconfiguration allows the backend service to communicate with speaker-recognition services across Docker Compose projects. Sinceservices.pymanages both projects together, network lifecycle is handled appropriately.Verify whether
asr-servicesandopenmemory-mcpshould also use the shared network for consistency:🏁 Script executed:
Length of output: 352
I need to check how
OFFLINE_ASR_TCP_URIis configured and whether asr-services actually runs services that need cross-project network access.Now I need to verify what
OFFLINE_ASR_TCP_URIis configured to and whether asr-services runs services that need the shared network:The web search didn't provide clarity on the specific codebase's asr-services. Let me check the actual configuration files directly:Based on the verification results and Docker Compose networking documentation, I have enough information to generate the rewritten review comment. The key findings are:
However, the key insight is that asr-services and openmemory-mcp are not explicitly configured to use the shared network, yet the backend references ASR services. This represents a potential missing configuration issue that requires the developer to verify whether these services need the shared network.
Configuration inconsistency: asr-services and openmemory-mcp should also use friend-network for cross-project communication.
The backend service references
OFFLINE_ASR_TCP_URI, indicating a need for cross-project communication with services managed throughservices.py. Currently, only speaker-recognition uses thefriend-network, but asr-services and openmemory-mcp have no explicit network configuration, leaving them in isolated project-specific networks. By default, docker-compose projects run in separate networks; however, by creating an external network and declaring it in every project, containers from different projects can talk with each other.Add network configuration to asr-services and openmemory-mcp docker-compose files:
networksblock withname: friend-network(matching speaker-recognition)services.py🤖 Prompt for AI Agents