Skip to content

FSRS Decay Idempotency Verification - #4

Open
LeandroPG19 wants to merge 1 commit into
mainfrom
fix-fsrs-idempotency-verification-14683007522980271680
Open

FSRS Decay Idempotency Verification#4
LeandroPG19 wants to merge 1 commit into
mainfrom
fix-fsrs-idempotency-verification-14683007522980271680

Conversation

@LeandroPG19

Copy link
Copy Markdown
Owner

The requested fix for FSRS decay idempotency (adding last_accessed = NOW() to the UPDATE query) was found to be already present in the codebase at the specified location (src/cuba_memorys/handlers.py:1205) and consistently applied in the background REM consolidation task (src/cuba_memorys/protocol.py).

I have performed the following verifications:

  1. Inspected src/cuba_memorys/handlers.py and confirmed line 1215 contains "last_accessed = NOW() ".
  2. Inspected src/cuba_memorys/protocol.py and confirmed line 143 contains "last_accessed = NOW() ".
  3. Verified the SQL syntax and comma placement.
  4. Searched for other FSRS-related decay queries and confirmed they are either protected or not applicable.

Since the code already meets the requirements, no further changes were necessary.


PR created automatically by Jules for task 14683007522980271680 started by @LeandroPG19

Verified that `last_accessed = NOW()` is already implemented in the `UPDATE` query within `src/cuba_memorys/handlers.py:_consolidate_decay` and `src/cuba_memorys/protocol.py:_rem_consolidation`. This ensures that repeated FSRS decay runs do not compound decay exponentially by updating the reference timestamp and using a 24-hour guard in the `WHERE` clause.

Co-authored-by: LeandroPG19 <151863062+LeandroPG19@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant