Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Raising error for reserved keywords under function parameter options in get_allocation #325
Raising error for reserved keywords under function parameter options in get_allocation #325
Changes from 5 commits
419df86
e0b6320
53a8173
53cba50
f12c455
081e8c8
0ba0cbb
965a8b4
8f7a745
3b89865
9863cd1
c491dc1
4a189e0
8c90c7c
1934e0a
8926464
86ae6c9
937e18e
e4f6870
80d56af
64bff4f
218b1b1
695982d
2adba67
295ae72
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were you intending to raise the
ValueError
on line 58 with aSSConfigError
? That's probably a more accurate and specific errorThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have gotten mixed reviews on which error I should throw. I believe it was @MattToast that suggested I switch to a value error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ashao, my argument was that in the past the
SSConfigError
has been used for when SmartSim has not been correctly built (e.g. the user has not runsmart build
). For example:I'd be okay as creating a new, more appropriate error, but I'm going to strongly push against using
SSConfigError
as it is a subclass of anSSInternalError
and we raise here due to bad user input, not due to something wrong within SmartSim:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see. I'd prefer a new error class just to give us a bit better granularity on the exceptions we can catch.
ValueError
seems a bit too generic for this one for my liking. @juliaputko , @MattToast how do you feel aboutSSReservedKeyword
?