Multiple severe bug fixes #9
Closed
Conversation
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
Enhanced logging in load-shedding middleware and server initialization to provide better visibility into system resource management. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Enhanced resource cleanup across multiple components including session management, caching, and client connections. Added proper cleanup handlers and improved shutdown procedures to prevent memory leaks. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Improved heap usage calculation and memory tracking to prevent false positives in load shedding logic. Enhanced budget management and compression handling for more accurate memory monitoring. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Fixed constraint violation in memory extractor that was causing database errors when entity types exceeded allowed values. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
…acters
Enhanced the prepareFTS5Query() function to sanitize all special characters
that could cause FTS5 syntax errors, including pipes (|), commas (,), and
other punctuation marks that appear in markdown tables and formatted text.
Changes:
- Expanded character removal regex to include: | , + = ? ! ; / \ @ # $ % ^ & { }
- Added additional safety check to remove any remaining non-alphanumeric characters
- Prevents "fts5: syntax error near ','" errors when searching with complex queries
The fix resolves FTS5 syntax errors that occurred when Claude CLI sent
messages containing markdown tables or other formatted text with special
characters.
MichaelAnders
force-pushed
the
truly-clean-fixes
branch
from
e06b70d to
a0a17ea
Compare
Author
|
One issue to fix with claude versions above 2.1.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Lynkr failed most of the time for me: responses took ages, very many errors in the log output - unusable (remote RTX 3090).
With these changes (&thx to Claude), Ollama interactions are now fast (ollama is done - you get the response) and no more errors!