From 672e2f28b70f63c5ed440e9f0beb10fd80dfea42 Mon Sep 17 00:00:00 2001 From: Arkadiy Kukarkin Date: Tue, 14 Apr 2026 11:05:35 +0200 Subject: [PATCH] log wallet_assignments migration progress in export-keys With large wallet_assignments tables (observed 719 rows in production), migrateWalletAssignments runs long enough that users wonder if the command is hung. Emit an info log at the start of the migration showing the row count, so users see progress between the per-key export logs and the final 'migrated N' summary. --- handler/wallet/export_keys.go | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/handler/wallet/export_keys.go b/handler/wallet/export_keys.go index e30d68d0a..05069364e 100644 --- a/handler/wallet/export_keys.go +++ b/handler/wallet/export_keys.go @@ -81,6 +81,10 @@ func migrateWalletAssignments(db *gorm.DB) error { return errors.Wrap(err, "failed to read wallet_assignments") } + if len(rows) > 0 { + logger.Infow("migrating wallet_assignments to preparation.wallet_id", "count", len(rows)) + } + migrated := 0 for _, r := range rows { // find the new wallet by actor_id