Conversation
There was a problem hiding this comment.
Pull request overview
Fixes a client/server behavior mismatch where dry_run=False was previously omitted from query params, causing the server to apply its default (True) and unintentionally run in dry-run mode.
Changes:
- Always include the
dry_runquery parameter when calling the long-term memory “forget” endpoint. - Adds an inline comment explaining why
dry_runmust be passed explicitly.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
abrookins
left a comment
There was a problem hiding this comment.
Good catch! Can you add a test?
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
abrookins
left a comment
There was a problem hiding this comment.
LGTM - thanks for jumping on this! 👍
dry-runis a boolean, so was not being added toparams[]when set toFalse. The server defaulted toTruein all cases.Note
Medium Risk
Changes the
forget_long_term_memoriesrequest semantics sodry_run=Falseresults in real deletions instead of silently using the server default (True); this could unexpectedly delete data for callers who previously relied on the buggy behavior. Otherwise the change is small and covered by updated unit tests.Overview
Fixes
forget_long_term_memoriesto always include the booleandry_runquery param (including whenFalse), avoiding the server’s default ofdry_run=Truefrom being applied unintentionally.Updates tests to assert the exact
POST /v1/long-term-memory/forgetcall parameters for basic, dry-run, and filtered forget requests.Written by Cursor Bugbot for commit 545eeb2. This will update automatically on new commits. Configure here.