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 }}
Repository navigation
dashmate group core reindex skips the DKG-safe stop check and hides which node failed #5857
dashmate group core reindex (packages/dashmate/src/commands/group/core/reindex.js) has two problems.
It skips the DKG-safe stop check. To skip the per-node confirmation prompt, it sets ctx.isForce = true before running each node's reindexNodeTask. The stop task reads the same flag, so the masternodes are stopped without checking whether they are in a DKG session. Stopping a member mid-session risks a PoSe penalty.
Its per-node tasks have no titles. It runs new Listr(configGroup.map((config) => ({ task: () => reindexNodeTask(config) }))). listr2's default renderer leaves out a subtree whose tasks all lack a title, so when a node fails, the output shows neither which node nor why. feat(dashmate): show what a DKG-safe stop waits for and how long #5843 adds titles to the same pattern in restart, group stop and group restart.
Possible fixes
Skip the prompt with a dedicated context flag instead of isForce, so the DKG check still runs. Offer --force to skip it explicitly.
Title each node's task, e.g. Reindex ${config.getName()} node.
Activity