You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 22, 2025. It is now read-only.
panic!("We are attempting to dump a block that we produced. \
1244
+
This indicates that we are producing duplicate blocks, \
1245
+
or that there is a bug in our runtime/replay code which \
1246
+
causes us to compute different bank hashes than the rest of the cluster. \
1247
+
We froze slot {duplicate_slot} with hash {frozen_hash:?} while the cluster hash is {correct_hash}");
1248
+
}
1249
+
1235
1250
Self::purge_unconfirmed_duplicate_slot(
1236
1251
*duplicate_slot,
1237
1252
ancestors,
@@ -1249,7 +1264,11 @@ impl ReplayStage {
1249
1264
.and_modify(|x| *x += 1)
1250
1265
.or_insert(1);
1251
1266
if*attempt_no > MAX_REPAIR_RETRY_LOOP_ATTEMPTS{
1252
-
panic!("We have tried to repair duplicate slot: {} more than {} times and are unable to freeze a block with bankhash {}, instead we have a block with bankhash {:?}. This is most likely a bug in the runtime. At this point manual intervention is needed to make progress. Exiting",*duplicate_slot,MAX_REPAIR_RETRY_LOOP_ATTEMPTS,*correct_hash, frozen_hash);
1267
+
panic!("We have tried to repair duplicate slot: {duplicate_slot} more than {MAX_REPAIR_RETRY_LOOP_ATTEMPTS} times \
1268
+
and are unable to freeze a block with bankhash {correct_hash}, \
1269
+
instead we have a block with bankhash {frozen_hash:?}. \
1270
+
This is most likely a bug in the runtime. \
1271
+
At this point manual intervention is needed to make progress. Exiting");
1253
1272
}
1254
1273
warn!(
1255
1274
"Notifying repair service to repair duplicate slot: {}, attempt {}",
@@ -1266,8 +1285,8 @@ impl ReplayStage {
1266
1285
}
1267
1286
};
1268
1287
1269
-
// If we purged/repaired, then no need to keep the slot in the set of pending work
1270
-
!did_purge_repair
1288
+
// If we dumped/repaired, then no need to keep the slot in the set of pending work
1289
+
!did_dump_repair
1271
1290
});
1272
1291
1273
1292
// Notify repair of the dumped slots along with the correct hash
0 commit comments