Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow expander to return string representation of invalid operators #453

Merged

Conversation

douglasjacobsen
Copy link
Collaborator

This merge updates the way binary operators work in the Expander. Previously, if a string with binary operators was passed in (i.e. intel-mpi-benchmarks) the binary operators were expected to actually operate on numerical inputs. This caused unescaped string comparisons (i.e. {application_name} == intel-mpi-benchmarks) to fail as the expander would give a syntax error and not evaluate this statement.

This merge changes this behaivor to force the expander to return a string representation of the args and binary operator: (i.e. intel-mpi-benchmarks is returned as 'intel-mpi-benchmarks') to allow these types of comparisons.

@douglasjacobsen douglasjacobsen added bug Something isn't working enhancement New feature or request testing Modifications to testing labels Apr 4, 2024
This commit updates the way binary operators work in the Expander.
Previously, if a string with binary operators was passed in (i.e.
`intel-mpi-benchmarks`) the binary operators were expected to actually
operate on numerical inputs. This caused unescaped string comparisons
(i.e. `{application_name} == intel-mpi-benchmarks`) to fail as the
expander would give a syntax error and not evaluate this statement.

This commit changes this behaivor to force the expander to return a
string representation of the args and binary operator:
(i.e. `intel-mpi-benchmarks` is returned as `'intel-mpi-benchmarks'`) to
allow these types of comparisons.
@rfbgo rfbgo merged commit b1a98b3 into GoogleCloudPlatform:develop Apr 4, 2024
5 checks passed
@douglasjacobsen douglasjacobsen deleted the fix_strings_in_expander branch April 4, 2024 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request testing Modifications to testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants