From da484f659253090cbc352c8f2eef1d2455533b4e Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 28 Nov 2022 05:31:28 +0000 Subject: [PATCH] lei_mirror: require PublicInbox::Lock at use It's easier to understand why we lazy-load Lock for v2-only code paths when we require it near its first use. --- lib/PublicInbox/LeiMirror.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/PublicInbox/LeiMirror.pm b/lib/PublicInbox/LeiMirror.pm index 2b20873e..a7ddfcd2 100644 --- a/lib/PublicInbox/LeiMirror.pm +++ b/lib/PublicInbox/LeiMirror.pm @@ -384,6 +384,7 @@ sub v2_done { # called via OnDestroy my ($self) = @_; return if $self->{dry_run} || !$LIVE; my $dst = $self->{cur_dst} // $self->{dst}; + require PublicInbox::Lock; my $lk = bless { lock_path => "$dst/inbox.lock" }, 'PublicInbox::Lock'; my $lck = $lk->lock_for_scope($$); _write_inbox_config($self); @@ -461,7 +462,6 @@ failed to extract epoch number from $src (!$self->{dry_run} && !-d $dst) and File::Path::mkpath($dst); - require PublicInbox::Lock; my $fini = PublicInbox::OnDestroy->new($$, \&v2_done, $task); $lei->{opt}->{'inbox-config'} =~ /\A(?:always|v2)\z/s and -- 2.48.1