Skip to content

Conversation

@juan-g-bonilla
Copy link
Contributor

Description

Array sizes are now extracted from the array directly, instead of being passed as inputs to the function. This prevents some inconsistencies in how memory was copied, which triggered the original error.

Verification

Existing tests, many of which using recorders, pass. @Will-Schwend confirmed this fixes the issue on his branch, and his PR will contain a test that depends on this fix being correct.

Array sizes are now extracted from the array directly.
@juan-g-bonilla juan-g-bonilla self-assigned this Sep 21, 2025
@juan-g-bonilla juan-g-bonilla requested a review from a team as a code owner September 21, 2025 19:35
@juan-g-bonilla juan-g-bonilla added the bug Something isn't working label Sep 21, 2025
@juan-g-bonilla juan-g-bonilla moved this to 👀 In review in Basilisk Sep 21, 2025
@juan-g-bonilla juan-g-bonilla merged commit 258edc5 into develop Sep 21, 2025
12 checks passed
@juan-g-bonilla juan-g-bonilla deleted the fix/1097-2d-recorder branch September 21, 2025 22:02
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Basilisk Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Recorder not working in unit test

3 participants