comments

src/perf_counter/perf_counter_atomic.h

@@ -439,8 +439,7 @@ class perf_counter_number_percentile_atomic : public perf_counter
                   const boost::system::error_code &ec)
     {
         // as the callback is not in tls context, so the log system calls like LOG_INFO, dassert
-        // will
-        // cause a lock
+        // will cause a lock
         if (!ec) {
             calc(boost::make_shared<compute_context>());
 

src/replica/duplication/mutation_batch.cpp

@@ -60,8 +60,8 @@ void mutation_buffer::commit(decree d, commit_type ct)
         //             n+m(m>1)            n+k(k>=m)
         //
         // just LOG_ERROR but not dassert if mutation loss or other problem, it's different from
-        // base
-        // class implement. And from the error and perf-counter, we can choose restart duplication
+        // base class implement. And from the error and perf-counter, we can choose restart
+        // duplication
         // or ignore the loss.
         if (next_committed_mutation == nullptr || !next_committed_mutation->is_logged()) {
             derror_replica("mutation[{}] is lost in prepare_list: "