Wallet fixes for Knots 29.3 by luke-jr · Pull Request #249 · bitcoinknots/bitcoin

luke-jr · 2026-01-22T14:53:39Z

This is a cherry-picking of multiple fix branches (including Core 29.3 backports) for review purposes

Github-Pull: bitcoin#31423 Rebased-From: d04f6a9

Github-Pull: bitcoin#31423 Rebased-From: 1de423e

Github-Pull: bitcoin#34215 Rebased-From: f78f6f1

Track what RestoreWallet creates so only those files and directories are removed during a failure and nothing else. Preexisting paths must be left untouched. Note: Using fs::remove_all() instead of fs::remove() in RestoreWallet does not cause any problems currently, but the change is necessary for the next commit which extends RestoreWallet to work with existing directories, which may contain files that must not be deleted. Github-Pull: bitcoin#34156 Rebased-From: 4ed0693

When migrating any legacy unnamed wallet, a failed migration would cause the cleanup logic to remove its parent directory. Since this type of legacy wallet lives directly in the main '/wallets/' folder, this resulted in unintentionally erasing all wallets, including the backup file. To be fully safe, we will no longer call `fs::remove_all`. Instead, we only erase the individual db files we have created, leaving everything else intact. The created wallets parent directories are erased only if they are empty. As part of this last change, `RestoreWallet` was modified to allow an existing directory as the destination, since we no longer remove the original wallet directory (we only remove the files we created inside it). This also fixes the restore of top-level default wallets during failures, which were failing due to the directory existence check that always returns true for the /wallets/ directory. This bug started after: bitcoin@f6ee59b Previously, the `fs::copy_file` call was failing for top-level wallets, which prevented the `fs::remove_all` call from being reached. Github-Pull: bitcoin#34156 Rebased-From: f4c7e28

Verifies that a failed migration of the unnamed (default) wallet does not erase the main /wallets/ directory, and also that the backup file exists. Github-Pull: bitcoin#34156 Rebased-From: 36093bd

…rune failure The first test verifies that restoring into an existing empty directory or a directory with no .dat db files succeeds, while restoring into a dir with a .dat file fails. The second test covers restoring into the default unnamed wallet (wallet.dat), which also implicitly exercises the recovery path used after a failed migration. The third test covers failure during restore on a prune node. When the wallet last sync was beyond the pruning height. Github-Pull: bitcoin#34156 Rebased-From: f011e0f

Right now, after migration the last message users see is "migration completed", but the migration isn't actually finished yet. We still need to load the new wallets to ensure consistency, and if that fails, the migration will be rolled back. This can be confusing for users. This change logs the post-migration loading step and if a wallet fails to load and the migration will be rolled back. Github-Pull: bitcoin#34156 Rebased-From: d70b159

Because the default wallet has no name, the watch-only and solvables wallets created during migration end up having no name either. This fixes it by applying the same prefix name we use for the backup file for an unnamed default wallet. Before: watch-only wallet named "_watchonly" After: watch-only wallet named "default_wallet_watchonly" Github-Pull: bitcoin#34156 Rebased-From: 82caa81

…eight Github-Pull: bitcoin#34156 Rebased-From: b7c34d0

Refactor a common way to perform the failed migration test that exists for default wallets, and add relative-path wallets and absolute-path wallets. Github-Pull: 34226 Rebased-From: eeaf28d

This check ensures that when migrating a legacy wallet with a direct filename, the backup file is named as expected. Co-authored-by: Ava Chow <github@achow101.com> Github-Pull: bitcoin#32273 Rebased-From: e22c359

Co-authored-by: Russell Yanofsky <russ@yanofsky.org> Github-Pull: bitcoin#32273 Rebased-From: 70f1c99

Github-Pull: bitcoin#32273 Rebased-From: 63c6d36

Github-Pull: bitcoin#32273 Rebased-From: 41faef5

Github-Pull: bitcoin#32273 Rebased-From: f0bb3d5

Github-Pull: bitcoin#32273 Rebased-From: 76fe0e5

…allet If any other files exist in the directory, we cannot assume the sharable files are exclusively for this wallet. But if they are, this also cleans up other log.* files

…ils, log the correct wallet name in error message

…eason Since we no longer delete the wallet directory, there's no need to vacate it The moving only served to risk errors by crossing filesystem boundaries (which fs::rename can't handle)

…ating from non-directory While 30.x+ keep backup files in walletdir, 29.x places them in the migrated wallet directory

…et, but not with a shared db environment

Github-Pull: bitcoin#32984 Rebased-From: 060695c

Github-Pull: bitcoin#34226 Rebased-From: eeaf28d

…node_fails Github-Pull: bitcoin#34156 Rebased-From: b7c34d0

…ucceed properly

…ectory itself

Wallet creation/opening errors turn into RPC_MISC_ERROR without this

Github-Pull: bitcoin#31423 Rebased-From: e86d71b

…legacy wallet Currently, the migration process creates a brand-new descriptor wallet with no connection to the user's legacy wallet when the legacy wallet lacks key material and contains only watch-only scripts. This behavior is not aligned with user expectations. If the legacy wallet contains only watch-only scripts, the migration process should only generate a watch-only wallet instead. Github-Pull: bitcoin#31423 Rebased-From: b789907

After a wallet is migrated and we are trying to load it, if it could not be loaded, don't try to set the wallet name. Github-Pull: bitcoin#32984 Rebased-From: 8a4cfdd

- Comment updates - Use fs::remove when deleting empty migration target - Adapt tests to only having watchonly migration output where applicable - break out of wallet reload loop when any fail Originally-From: f4c7e28 and d70b159 and 82caa81 (bitcoin#34156)

…point and lsn_reset

…atabase" subdirectory Otherwise, there's a race condition if another program/instance opens a wallet before we delete it

…irectory

…tdown It's hypothetically possible, albeit difficult to arrange, that other non-loaded wallets are still relying on it

…vironment::Close() This reverts commit 8a06c8cf55f67934a4d86732217e38e42ac5198e.

… BerkeleyEnvironment::Flush

kwsantiago · 2026-01-26T19:18:26Z

+    std::vector<fs::path> Files() override
+    {
+        std::vector<fs::path> files;
+        files.emplace_back(m_dir_path / fs::PathFromString(m_file_path));


m_file_path is already the full absolute path (used directly for sqlite3_open_v2). The / operator with an absolute RHS ignores the LHS. Consider using fs::PathFromString(m_file_path) directly.

Where is m_file_path guaranteed to be absolute?

m_file_path is always absolute in practice, since it comes from SQLiteDataFile(path) which returns a full path. So the m_dir_path / is silently ignored by operator/. The code works but is misleading.

Using fs::PathFromString(m_file_path) directly would be correct either way.

kwsantiago · 2026-01-26T19:18:42Z

+    };
+    try {
+        if (build_files_list(files, env, m_filename)) return files;
+    } catch (...) {


Catching all exceptions silently could mask filesystem errors and lead to incomplete cleanup. Consider logging when falling back to the smaller file list.

Might be a good idea, but I don't see a good way to do it. We build the file list even if we don't delete them later.

The fallback (line 391) just returns the single wallet file, so the failure mode is conservative (fewer files deleted, not more). Logging would be noisy since Files() is called even when no deletion follows.

luke-jr · 2026-02-10T16:45:18Z

Merged in v29.3.knots20260210

Copilot

Pull request overview

This PR implements wallet fixes for Knots 29.3, cherry-picking multiple fix branches including Core 29.3 backports. The changes focus on wallet migration improvements, directory permission checks, safer cleanup during failed operations, and more robust error handling.

Changes:

Adds write-permission checks for wallet directories before opening databases, and improves RestoreWallet to handle pre-existing directories without overwriting database files.
Refactors wallet migration to properly handle watch-only wallets (empty spendable wallets are discarded), relative/absolute paths, and uses safer file-level cleanup instead of fs::remove_all during failure recovery.
Adds a Files() virtual method to WalletDatabase for precise tracking of database files, changes BDB CheckpointLSN to return success/failure, and upgrades incompatible BDB warning to FATAL_ERROR.

Reviewed changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
`src/wallet/wallet.cpp`	Major migration logic refactor: backup naming, empty wallet handling, safer cleanup, path resolution
`src/wallet/bdb.cpp`	Add `Files()` impl, error handling for `CheckpointLSN`, writable dir check, catch exceptions in `MakeBerkeleyDatabase`
`src/wallet/bdb.h`	`CheckpointLSN` returns bool, add `Files()` declaration
`src/wallet/sqlite.cpp`	Writable directory check, type change for `m_dir_path`
`src/wallet/sqlite.h`	`m_dir_path` changed to `fs::path`, add `Files()` impl
`src/wallet/db.h`	Add pure virtual `Files()` method
`src/wallet/dump.cpp`	Use `Files()` for targeted cleanup instead of `remove_all`
`src/wallet/salvage.cpp`	Add `Files()` to `DummyDatabase`
`src/wallet/migrate.h`	Add `Files()` to `BerkeleyRODatabase`
`src/wallet/test/util.h`	Add `Files()` to `MockableDatabase`
`src/util/fs_helpers.h` / `.cpp`	Add `IsDirWritable()` utility function
`src/qt/walletcontroller.cpp`	Use original wallet name in migration success message
`CMakeLists.txt`	Upgrade incompatible BDB warning to `FATAL_ERROR`
`test/functional/wallet_migration.py`	Extensive new tests for migration edge cases
`test/functional/wallet_backup.py`	Tests for restore into existing dirs and unnamed wallets
`test/functional/wallet_startup.py`	Test loading unwritable wallet
`test/functional/wallet_createwallet.py`	Test creating wallet in unwritable directory
`test/functional/wallet_multiwallet.py`	Simplify error code expectation
`test/functional/tool_wallet.py`	Tests for `createfromdump` with unnamed wallet
`test/functional/test_framework/util.py`	Add `is_dir_writable()` helper

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-09T21:10:56Z

+        files.emplace_back(m_dir_path / fs::PathFromString(m_file_path));
+        files.emplace_back(m_dir_path / fs::PathFromString(m_file_path + "-journal"));


m_file_path is a full absolute file path string (set via fs::PathToString(file_path) where file_path is an absolute path from the constructor). Joining m_dir_path / fs::PathFromString(m_file_path) will produce an incorrect path because you're appending an absolute path to another path. This should use just the filename component, e.g., fs::PathFromString(m_file_path).filename(), or simply use fs::PathFromString(m_file_path) directly without prepending m_dir_path.

Suggested change

files.emplace_back(m_dir_path / fs::PathFromString(m_file_path));

files.emplace_back(m_dir_path / fs::PathFromString(m_file_path + "-journal"));

files.emplace_back(fs::PathFromString(m_file_path));

files.emplace_back(fs::PathFromString(m_file_path + "-journal"));

Copilot · 2026-03-09T21:10:57Z

    fs::path this_wallet_dir = fs::absolute(fs::PathFromString(local_wallet->GetDatabase().Filename())).parent_path();
-    fs::path backup_filename = fs::PathFromString(strprintf("%s_%d.legacy.bak", (wallet_name.empty() ? "default_wallet" : wallet_name), GetTime()));
+    const std::string backup_prefix = wallet_name.empty() ? MigrationPrefixName(*local_wallet) : [&] {
+        // fs::weakly_canonical resolves relative specifiers and remove trailing slashes.


The comment on line 4668 says "remove trailing slashes" (singular verb form). It should read "removes trailing slashes" to be grammatically correct.

Suggested change

// fs::weakly_canonical resolves relative specifiers and remove trailing slashes.

// fs::weakly_canonical resolves relative specifiers and removes trailing slashes.

Copilot · 2026-03-09T21:10:57Z

-            shutil.copytree(self.old_node.wallets_path / wallet_name, self.master_node.wallets_path / wallet_name)
+            src = os.path.abspath(self.old_node.wallets_path / wallet_name)
+            dst = os.path.abspath(self.master_node.wallets_path / wallet_name)
+            if src != dst :


There is a trailing space before the colon. Remove the extra space to follow standard Python style conventions.

Suggested change

if src != dst :

if src != dst:

Copilot · 2026-03-09T21:10:57Z

+        assert not (self.master_node.wallets_path / f"{wallet_name}_watchonly").exists()
+        # Since the file in failed_solvables is one that we put there, migration shouldn't touch it
+        assert os.path.exists(solvables_path)
+        new_shasum = sha256sum_file(os.path.join(solvables_path , "wallet.dat"))


There is an extra space before the comma in os.path.join(solvables_path , "wallet.dat"). Remove it for consistent formatting.

Suggested change

new_shasum = sha256sum_file(os.path.join(solvables_path , "wallet.dat"))

new_shasum = sha256sum_file(os.path.join(solvables_path, "wallet.dat"))

Copilot · 2026-03-09T21:10:58Z

+        self.start_node(self.old_node.index)
+        self.connect_nodes(1, 0)
+
+    def unsynced_wallet_on_pruned_node_fails(self):


This method name does not follow the test_ prefix convention used by all other test methods in this class (e.g., test_loading_failure_after_migration, test_failed_migration_cleanup). It should be renamed to test_unsynced_wallet_on_pruned_node_fails for consistency. The call site at line 1785 would also need to be updated.

Copilot · 2026-03-09T21:10:58Z

        err = strprintf(_("Error initializing wallet database environment %s!"), fs::quoted(fs::PathToString(Directory())));
        if (ret == DB_RUNRECOVERY) {
-            err += Untranslated(" ") + _("This error could occur if this wallet was not shutdown cleanly and was last loaded using a build with a newer version of Berkeley DB. If so, please use the software that last loaded this wallet");
+            err += Untranslated(" ") + _("This error could occur if this wallet was last loaded using a build with a newer version of Berkeley DB.");


The original message provided the user with guidance about what to do ("please use the software that last loaded this wallet"). The updated message only states a potential cause without offering any actionable advice for the user.

Suggested change

err += Untranslated(" ") + _("This error could occur if this wallet was last loaded using a build with a newer version of Berkeley DB.");

err += Untranslated(" ") + _("This error could occur if this wallet was last loaded using a build with a newer version of Berkeley DB. Please use the software that last loaded this wallet.");

Copilot · 2026-03-09T21:10:58Z

    if(WARN_INCOMPATIBLE_BDB)
-      message(WARNING "If this is intended, pass \"-DWARN_INCOMPATIBLE_BDB=OFF\".\n"
+      message(FATAL_ERROR "If this is intended, pass \"-DWARN_INCOMPATIBLE_BDB=OFF\".\n"
                      "Passing \"-DWITH_BDB=OFF\" will suppress this warning."


The message text still says "will suppress this warning" but the severity has been changed from WARNING to FATAL_ERROR. The text should be updated to say something like "will suppress this error" to match the new behavior.

Suggested change

"Passing \"-DWITH_BDB=OFF\" will suppress this warning."

"Passing \"-DWITH_BDB=OFF\" will suppress this error."

Copilot · 2026-03-09T21:10:58Z

+        open(survive_path, "wb").close()
+        assert survive_path.exists()
+        if migrating_file_to_dir:
+            survive2_path = master_path.parent / "survive"
+        else:
+            survive2_path = master_path / "survive"
+        open(survive2_path, "wb").close()


Using open(...).close() without a with statement is a common anti-pattern. Consider using survive_path.touch() (from pathlib.Path) instead, which is both cleaner and already used elsewhere in the test suite (e.g., extra_file.touch() in wallet_backup.py). This also applies to line 752.

Suggested change

open(survive_path, "wb").close()

assert survive_path.exists()

if migrating_file_to_dir:

survive2_path = master_path.parent / "survive"

else:

survive2_path = master_path / "survive"

open(survive2_path, "wb").close()

survive_path.touch()

assert survive_path.exists()

if migrating_file_to_dir:

survive2_path = master_path.parent / "survive"

else:

survive2_path = master_path / "survive"

survive2_path.touch()

furszy and others added 30 commits January 22, 2026 14:42

refactor: remove sqlite dir path back-and-forth conversion

1b93696

Github-Pull: bitcoin#31423 Rebased-From: d04f6a9

wallet: introduce method to return all db created files

ed5a572

Github-Pull: bitcoin#31423 Rebased-From: 1de423e

wallettool: do not use fs::remove_all in createfromdump cleanup

5932c88

Github-Pull: bitcoin#34215 Rebased-From: f78f6f1

test: add coverage for unnamed wallet migration failure

57c77af

Verifies that a failed migration of the unnamed (default) wallet does not erase the main /wallets/ directory, and also that the backup file exists. Github-Pull: bitcoin#34156 Rebased-From: 36093bd

test: coverage for migration failure when last sync is beyond prune h…

73efce7

…eight Github-Pull: bitcoin#34156 Rebased-From: b7c34d0

wallet: test: Failed migration cleanup

4597822

Refactor a common way to perform the failed migration test that exists for default wallets, and add relative-path wallets and absolute-path wallets. Github-Pull: 34226 Rebased-From: eeaf28d

NOTE: Core 29.3rc1 changes

c7f4304

test: wallet: Check direct file backup name.

ee1effc

This check ensures that when migrating a legacy wallet with a direct filename, the backup file is named as expected. Co-authored-by: Ava Chow <github@achow101.com> Github-Pull: bitcoin#32273 Rebased-From: e22c359

wallet: Fix migration of wallets with pathnames.

22b3cab

Co-authored-by: Russell Yanofsky <russ@yanofsky.org> Github-Pull: bitcoin#32273 Rebased-From: 70f1c99

test: Migration of a wallet with ../ in path.

994f248

Github-Pull: bitcoin#32273 Rebased-From: 63c6d36

test: Migration fail recovery w/ ../ in path

e48ad86

Github-Pull: bitcoin#32273 Rebased-From: 41faef5

test: Migration of a wallet ending in /

5ad329c

Github-Pull: bitcoin#32273 Rebased-From: f0bb3d5

test: Migration of a wallet ending in ../

8b324ab

Github-Pull: bitcoin#32273 Rebased-From: 76fe0e5

NOTE: fix_walletmigrate_relpaths-29.3

9095a28

Wallet/bdb: Safely and correctly list files only used by the single w…

878cfe6

…allet If any other files exist in the directory, we cannot assume the sharable files are exclusively for this wallet. But if they are, this also cleans up other log.* files

Wallet/Migration: If loading the new watchonly or solvables wallet fa…

e3e893a

…ils, log the correct wallet name in error message

Wallet/Migration: Skip moving the backup file back and forth for no r…

3b5f7d7

…eason Since we no longer delete the wallet directory, there's no need to vacate it The moving only served to risk errors by crossing filesystem boundaries (which fs::rename can't handle)

Bugfix: Wallet/Migration: Move backup into wallet directory when migr…

20196a9

…ating from non-directory While 30.x+ keep backup files in walletdir, 29.x places them in the migrated wallet directory

QA: tool_wallet: Check that db.log is deleted with a lone legacy wall…

1d4be93

…et, but not with a shared db environment

NOTE: fix_34222_backport

9ae0bf9

test: Failed load after migrate should restore backup

4235863

Github-Pull: bitcoin#32984 Rebased-From: 060695c

QA: wallet_migration: Use assert_is_bdb in test_migration_failure

aafcad1

Github-Pull: bitcoin#34226 Rebased-From: eeaf28d

QA: wallet_migration: Use assert_is_bdb in unsynced_wallet_on_pruned_…

d6300b7

…node_fails Github-Pull: bitcoin#34156 Rebased-From: b7c34d0

QA: wallet_migration: Test that all the failed migration cases also s…

1ec9cf0

…ucceed properly

QA: wallet_migration: Test survival of a file in the wallet-owned dir…

9b55389

…ectory itself

luke-jr and others added 9 commits January 22, 2026 14:49

NOTE: handle_wallet_dir_nonwritable-29.2

20c0e92

Bugfix: Wallet/bdb: Catch exceptions in MakeBerkeleyDatabase

f327a14

Wallet creation/opening errors turn into RPC_MISC_ERROR without this

Wallet/bdb: improve error msg when db directory is not writable

fef351e

NOTE: handle_wallet_dir_nonwritable_bdb-29.2

a2c3c2e

wallet: refactor, dedup wallet re-loading code

735c672

Github-Pull: bitcoin#31423 Rebased-From: e86d71b

wallet: Set migrated wallet name only on success

860899b

After a wallet is migrated and we are trying to load it, if it could not be loaded, don't try to set the wallet name. Github-Pull: bitcoin#32984 Rebased-From: 8a4cfdd

NOTE: wallet_migrate_watchonly_only-29.3

8f26d9d

luke-jr added the bug label Jan 22, 2026

luke-jr added this to the 29.3 milestone Jan 22, 2026

luke-jr added 8 commits January 23, 2026 20:48

Bugfix: wallet/bdb: Check for and safely handle errors from txn_check…

6cd7024

…point and lsn_reset

Bugfix: wallet/bdb: Only release walletdir lock after deleting BDB "d…

0b647e8

…atabase" subdirectory Otherwise, there's a race condition if another program/instance opens a wallet before we delete it

Bugfix: wallet/bdb: Catch and handle exceptions deleting "database" d…

cfd2ca7

…irectory

Bugfix: wallet/bdb: Don't nuke "database" directory even on clean shu…

c6ed339

…tdown It's hypothetically possible, albeit difficult to arrange, that other non-loaded wallets are still relying on it

wallet/bdb: Remove no-longer-needed do_unlock parameter of BerkeleyEn…

281045e

…vironment::Close() This reverts commit 8a06c8cf55f67934a4d86732217e38e42ac5198e.

Bugfix: wallet/bdb: Actually set db refcount to -1 after lsn_reset in…

0f4c4f7

… BerkeleyEnvironment::Flush

build: Promote incompatible-bdb warning to a fatal error

6329bf9

NOTE: fix_bdb_edge_cases_202601-29

cf43a63

luke-jr force-pushed the knots29.3_walletfixes branch from b8561d2 to cf43a63 Compare January 23, 2026 20:49

kwsantiago reviewed Jan 26, 2026

View reviewed changes

Comment thread src/wallet/wallet.cpp

kwsantiago reviewed Jan 26, 2026

View reviewed changes

Comment thread src/wallet/wallet.cpp

kwsantiago reviewed Jan 26, 2026

View reviewed changes

Comment thread src/wallet/wallet.cpp

luke-jr added the merged label Feb 10, 2026

luke-jr requested a review from Copilot March 9, 2026 21:04

Copilot started reviewing on behalf of luke-jr March 9, 2026 21:04 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

		files.emplace_back(m_dir_path / fs::PathFromString(m_file_path));
		files.emplace_back(m_dir_path / fs::PathFromString(m_file_path + "-journal"));

	// fs::weakly_canonical resolves relative specifiers and remove trailing slashes.
	// fs::weakly_canonical resolves relative specifiers and removes trailing slashes.

	new_shasum = sha256sum_file(os.path.join(solvables_path , "wallet.dat"))
	new_shasum = sha256sum_file(os.path.join(solvables_path, "wallet.dat"))

	err += Untranslated(" ") + _("This error could occur if this wallet was last loaded using a build with a newer version of Berkeley DB.");
	err += Untranslated(" ") + _("This error could occur if this wallet was last loaded using a build with a newer version of Berkeley DB. Please use the software that last loaded this wallet.");

	"Passing \"-DWITH_BDB=OFF\" will suppress this warning."
	"Passing \"-DWITH_BDB=OFF\" will suppress this error."

Conversation

luke-jr commented Jan 22, 2026

Uh oh!

kwsantiago Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

luke-jr Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

kwsantiago Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

kwsantiago Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

luke-jr Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

kwsantiago Feb 25, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

luke-jr commented Feb 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants