Skip to content

Comments

fix: use maxlock (not maxtemp) as default in Simple::purge()#13

Draft
Koan-Bot wants to merge 1 commit intocern-mig:masterfrom
atoomic:koan.atoomic/fix-simple-purge-maxlock-v2
Draft

fix: use maxlock (not maxtemp) as default in Simple::purge()#13
Koan-Bot wants to merge 1 commit intocern-mig:masterfrom
atoomic:koan.atoomic/fix-simple-purge-maxlock-v2

Conversation

@Koan-Bot
Copy link

Simple::purge() was using $self->{maxtemp} (300s) as the default for the
maxlock option instead of $self->{maxlock} (600s). This caused locked
elements to be cleaned up too early, potentially removing locks that were
still legitimately held.

One-line fix: $self->{maxtemp}$self->{maxlock} on line 307.

Supersedes #2 (which included unrelated infrastructure commits).


🤖 Generated by Kōan

…le.pm

Simple::purge() was using $self->{maxtemp} as the default value for the
maxlock option instead of $self->{maxlock}. This caused locked elements
to be cleaned up after 300 seconds (maxtemp default) instead of the
intended 600 seconds (maxlock default), potentially removing locks that
were still legitimately held.
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