gmakstutis/graphiti
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add SEMAPHORE_LIMIT logging to startup configuration

Browse source 
Log the SEMAPHORE_LIMIT value at startup to help users verify their
concurrency control settings are being applied correctly. This is
especially useful when troubleshooting rate limit issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Lars Varming 2025-11-09 22:13:05 +01:00
parent 1dd3f6b337
commit ba938c9b9b
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
mcp_server/src/graphiti_mcp_server.py
View file

@ -1541,6 +1541,7 @@ async def initialize_server() -> ServerConfig:
logger.info(f' - Database: {config.database.provider}') logger.info(f' - Database: {config.database.provider}')
logger.info(f' - Group ID: {config.graphiti.group_id}') logger.info(f' - Group ID: {config.graphiti.group_id}')
logger.info(f' - Transport: {config.server.transport}') logger.info(f' - Transport: {config.server.transport}')
logger.info(f' - Semaphore Limit: {SEMAPHORE_LIMIT}')
# Log graphiti-core version # Log graphiti-core version
try: try: