-
Notifications
You must be signed in to change notification settings - Fork 143
refactor(shellcheck): fix all remaining warnings/errors #1019
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
Conversation
|
@jameslamb one more for you here |
jameslamb
left a comment
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.
I left a couple suggestions... leaving a blocking review because I think one is a correctness problem. The others are just small suggestions for improvement.
@ me whenever you want another review.
build.sh
Outdated
| if [[ ${CMAKE_TARGET} != "" ]]; then | ||
| echo "-- Compiling targets: ${CMAKE_TARGET}, verbose=${VERBOSE_FLAG}" | ||
| if [[ ${CMAKE_TARGET[*]} != "" ]]; then | ||
| echo "-- Compiling targets: ${CMAKE_TARGET[*]}, verbose=${VERBOSE_FLAG}" |
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.
| echo "-- Compiling targets: ${CMAKE_TARGET[*]}, verbose=${VERBOSE_FLAG}" | |
| echo "-- Compiling targets: ${CMAKE_TARGET[@]}, verbose=${VERBOSE_FLAG}" |
Similar to my comment above... I think here you want the values, not the keys (because there are no keys).
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.
Yeah, I think this is another weird implicit vs. explicit array concatenation thing -- shellcheck doesn't like it when strings and arrays are mixed: https://github.com/koalaman/shellcheck/wiki/SC2145
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.
huh, well, I'm definitely wrong here because that didn't output any values
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.
Hmm, or maybe CMAKE_TARGET was just empty? I've pushed up a different way of spelling this, in any case, but I think this should work.
> CMAKE_TARGET=('one' 'two')
> echo "-- Compiling targets: ${CMAKE_TARGET[*]}"
-- Compiling targets: one twoCo-authored-by: James Lamb <[email protected]>
Co-authored-by: James Lamb <[email protected]>
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.
Would it make sense (if it's possible) to exclude this file from cpp-ownership?
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.
I'd support that change.
437e909 to
b30809a
Compare
jameslamb
left a comment
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.
Approving, I think all of my comments have been addressed.
Thanks for finishing this one up! This project has a bit more shell code than RAPIDS repos, because it has bindings for so many languages and scripts to build those bindings. I think we'll be really glad to have shellcheck helping us with development here 😁
|
/merge |
Finishes up the shellcheck work tracked in rapidsai/build-planning#135