-
-
Notifications
You must be signed in to change notification settings - Fork 145
fix: add safety fallback for EMBEDDING_MAX_BATCH_SIZE parsing #249
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 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
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
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 123
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 235
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 3693
🏁 Script executed:
# Check FalkorDB version in requirements cat backend/app/database/falkor/code-graph-backend/requirements.txtRepository: AOSSIE-Org/Devr.AI
Length of output: 8289
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 44
🏁 Script executed:
# Read the full graph.py file to understand the context wc -l backend/app/database/falkor/code-graph-backend/api/graph.pyRepository: AOSSIE-Org/Devr.AI
Length of output: 125
🏁 Script executed:
# Read the graph.py file head -100 backend/app/database/falkor/code-graph-backend/api/graph.pyRepository: AOSSIE-Org/Devr.AI
Length of output: 3311
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 3311
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 391
🏁 Script executed:
Repository: AOSSIE-Org/Devr.AI
Length of output: 44
🌐 Web query:
FalkorDB 1.0.10 Python client exception types error handling💡 Result:
In FalkorDB Python client v1.0.10, almost all runtime errors you’ll handle are
redis-pyexceptions, because the client is a thin wrapper around aredis.Redis(...)connection and ultimately callsexecute_command(...)for FalkorDB commands. [1]Exception types you should expect
1) FalkorDB-py custom exception
falkordb.exceptions.SchemaVersionMismatchException(the only documented custom exception type in the package). [2]2) redis-py exceptions (primary ones to catch)
Catch from
redis.exceptions(sync) /redis.asyncio(async), typically:ResponseError: FalkorDB query/command errors (syntax errors, runtime errors like_AR_EXP_UpdateEntityIdx, etc.)ConnectionError: can’t connect / connection droppedTimeoutError: socket timeouts / blocked too longAuthenticationError: bad credentialsRedisError: base class for most redis-py client exceptionsPractical error-handling pattern
Notes:
FalkorDB==1.0.10reports), they will surface asredis.exceptions.ResponseErrorbecause the server returns an error reply. [1]from_url), not an exceptions redesign—so the above model is what you should rely on. [3]Sources:
[1] FalkorDB client builds on
redis.Redisand exposesexecute_command(readthedocs module source). (falkordb-py.readthedocs.io)[2]
SchemaVersionMismatchExceptiondefinition (readthedocs exceptions module). (falkordb-py.readthedocs.io)[3] v1.0.10 release notes / what changed. (github.com)
Citations:
Catch
redis.exceptions.ResponseErrorinstead of broadException.FalkorDB v1.0.10 is a thin wrapper around
redis-py, so "index already exists" errors surface asredis.exceptions.ResponseError, not a FalkorDB-specific exception type. CatchingExceptionmasks unrelated errors (connection failures, timeouts, authentication errors) that deserve different handling.While string-based matching for "already exists" is not ideal, it remains the only viable approach since there's no specific error code exposed. However, catching
ResponseErrorprovides better specificity:🤖 Prompt for AI Agents