BUG: Invoking SetData method with wrong parameter types

[dzenanz]

The signature is void SetData(TValue * datain, SizeValueType sz, bool LetArrayManageMemory)

This, by itself, is not a big problem. However, it might be a symptom of a larger problem.

PR Checklist

• No API changes were made (or the changes have been approved)
• No major design changes were made (or the changes have been approved)
• Added test (or behavior not changed)

[greptile-apps]

Greptile Summary

Corrects two memory-management test calls to pass the array size explicitly to SetData.

• Prevents false from being implicitly interpreted as a zero size.
• Preserves non-owning use of the stack-allocated buffer.

Confidence Score: 5/5

The PR appears safe to merge.

The changed test calls supply the required buffer length while retaining non-owning memory semantics, and no actionable failures remain.

T-Rex Logs

What T-Rex did

• The prerequisites for a Debug build were verified as missing, with cmake, ctest, and ninja not in PATH and no tooling installed.
• An attempt was made to run the requested Debug configuration command, which exited with code 127 because cmake was not found.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
Modules/Core/Common/test/itkArrayGTest.cxx	Both corrected calls now match the intended SetData(buffer, size, manageMemory) contract without changing production code.

_{Reviews (1): Last reviewed commit: "BUG: Invoking SetData method with wrong ..." | Re-trigger Greptile}

[hjmjohnson]

Confirmed correct, and worth landing as-is. The SetData(buffer, false) form promotes false to SizeValueType 0 with no diagnostic under -Wall -Wextra -Wconversion -Wsign-conversion, so both call sites were operating on empty arrays; the assertions could not detect it because they compare a size against the size it was just copied from.

Follow-up analysis and recommended paths recorded in #6718 — the API hazard that produced these two lines is still present, and itk::VariableLengthVector still carries the overload pair itk::Array dropped in 9e49264 (2016). This PR is a prerequisite for the Array guard proposed there.