-
Notifications
You must be signed in to change notification settings - Fork 330
Samza 1114 #69
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
Closed
Closed
Samza 1114 #69
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
52e7242
SAMZA-489
renato2099 3d77f2b
Merging
renato2099 393e46c
Merging Local
renato2099 84277c6
Merge branch 'master' of https://github.com/apache/samza
renato2099 77de76c
Sync with apache_master
renato2099 4cac3ae
SAMZA-1114: Improving script
renato2099 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
chk_gradle=$?Is this is just a way of checking
chk_gradlewhenset -eis set? Otherwise it would cause the shell to exit if any subcommand or pipeline returns a non-zero status?Wondering what's the need for this additional check using a
chk_gradleflag? It seems that-fshould already do the trick? (ifgradle_base_filedoes not exist)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.
hey @vjagadish1989 thanks for checking this out. The problem is that in my case the $(which gradle) command failed, and then the script exits without prompting anything, not even getting to the <-f> check.$(which gradle) into the variable chk_gradle so we can check if the $ (which gradle) didn't fail.
So this line puts the result of executing
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.
Firstly, Thanks for the patch @renato2099 👍
QQ: Did the command fail because
gradlewas not installed orwhichwas not installed? For the former, wouldn't the-fin the current implementation would catch it?I wrote a small test to verify this:
Check with valid gradle path:
Check with invalid gradle path:
Uh oh!
There was an error while loading. Please reload this page.
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.
Hey @vjagadish1989 thanks again for checking this out with me.
So on my env (Debian Lenny) the script exited when executing
which gradleand it didn't make it to theifstatement.whichwas installed because I didn't get acommand not founderror.I have also tried to reproduce the issue on different servers now and everything works as expected i.e.
whichdoesn't crash. I guess it was just something wrong with my local env. You can close this PR as this only affected me ;)