Skip to content

Conversation

@brendan-nasa
Copy link
Contributor

Closes #2008

@brendan-nasa brendan-nasa linked an issue Dec 10, 2025 that may be closed by this pull request
@brendan-nasa
Copy link
Contributor Author

@ddj116 @excaliburtb can y'all check this pr and see if it fixes y'all's issues

@coveralls
Copy link

Coverage Status

coverage: 55.909% (-0.01%) from 55.922%
when pulling b3ca16b on 2008-char-breaks-python-input-processor
into 3674388 on master.

@hchen99
Copy link
Contributor

hchen99 commented Dec 10, 2025

Thinking of adding tests for command_line_args_get_argc and command_line_args_get_argv in the CommandLineArguments test folder, and also adding tests to input.py under SIM_test_output_dir.

@ddj116
Copy link
Contributor

ddj116 commented Dec 10, 2025

@ddj116 @excaliburtb can y'all check this pr and see if it fixes y'all's issues

Can confirm this PR fixes the Ramtares use-case. Agree with @hchen99 if y'all can add a test for this it'll prevent it from ever popping up again. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

char** breaks python input processor

5 participants