Since we schedule the last chunk for commit in triggerSyncNow, we can assert that we will be fully synced on the next pull when it happens in the singleCommitter thread.

That allows for further simplification.

1 files changed, 2 insertions, 2 deletions

diff --git a/persistence/src/vespa/persistence/dummyimpl/dummy_bucket_executor.cpp b/persistence/src/vespa/persistence/dummyimpl/dummy_bucket_executor.cpp
index 3eda5146af1..060215c4521 100644
--- a/persistence/src/vespa/persistence/dummyimpl/dummy_bucket_executor.cpp
+++ b/persistence/src/vespa/persistence/dummyimpl/dummy_bucket_executor.cpp
@@ -6,7 +6,7 @@
 #include <vespa/vespalib/util/destructor_callbacks.h>
 
 using vespalib::makeLambdaTask;
-using vespalib::makeLambdaCallback;
+using vespalib::makeSharedLambdaCallback;
 
 namespace storage::spi::dummy {
 
@@ -32,7 +32,7 @@ DummyBucketExecutor::execute(const Bucket & bucket, std::unique_ptr<BucketTask>
             }
             _inFlight.insert(bucket.getBucket());
         }
-        bucketTask->run(bucket, makeLambdaCallback([this, bucket]() {
+        bucketTask->run(bucket, makeSharedLambdaCallback([this, bucket]() {
             std::unique_lock guard(_lock);
             assert(_inFlight.contains(bucket.getBucket()));
             _inFlight.erase(bucket.getBucket());