Fixing test that randomly fails because of an uninitialized buffer.

[KiterLuc]

---

TYPE: BUG
DESC: Fixing test failure because of an uninitialized buffer.

[eric-hughes-tiledb]

LGTM

A quick grep through the test sources showed 99 more instances of uninitialized char[n]. Some of them are output buffers, which are unlikely to be problematic, but I'm guessing there's more of this lurking.

[KiterLuc]

LGTM

A quick grep through the test sources showed 99 more instances of uninitialized char[n]. Some of them are output buffers, which are unlikely to be problematic, but I'm guessing there's more of this lurking.

I'll file a ticket for this.

[github-actions]

The backport to release-2.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-2.3 release-2.3
# Navigate to the new working tree
cd .worktrees/backport-release-2.3
# Create a new branch
git switch --create backport-2386-to-release-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick --mainline 1 f9e06292dfe97df110c19acde723b7d1abfd46c2
# Push it to GitHub
git push --set-upstream origin backport-2386-to-release-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-2.3

Then, create a pull request where the base branch is release-2.3 and the compare/head branch is backport-2386-to-release-2.3.