tks1197 opened a new pull request, #45052:
URL: https://github.com/apache/arrow/pull/45052

   <!--
   Thanks for opening a pull request!
   If this is your first pull request you can find detailed information on how 
   to contribute here:
     * [New Contributor's 
Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
     * [Contributing 
Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
   
   
   If this is not a [minor 
PR](https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes). 
Could you open an issue for this pull request on GitHub? 
https://github.com/apache/arrow/issues/new/choose
   
   Opening GitHub issues ahead of time contributes to the 
[Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.)
 of the Apache Arrow project.
   
   Then could you also rename the pull request title in the following format?
   
       GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
   
   or
   
       MINOR: [${COMPONENT}] ${SUMMARY}
   
   -->
   
   ### Rationale for this change
   
   ```bash
   ❯ pre-commit run --show-diff-on-failure --color=always --all-files shellcheck
   ShellCheck 
v0.10.0.......................................................Failed
   
   - hook id: shellcheck
   - exit code: 1
   
   In c_glib/test/run-test.sh line 20:
   test_dir="$(cd $(dirname $0); pwd)"
               ^--------------^ SC2164 (warning): Use 'cd ... || exit' or 'cd 
... || return' in case cd fails.
                  ^-----------^ SC2046 (warning): Quote this to prevent word 
splitting.
                            ^-- SC2086 (info): Double quote to prevent globbing 
and word splitting.
   
   Did you mean:
   test_dir="$(cd $(dirname "$0") || exit; pwd)"
   
   In c_glib/test/run-test.sh line 50:
     MODULE_TYPELIB_DIR_VAR_NAME="$(echo ${module} | tr a-z- A-Z_)_TYPELIB_DIR"
                                         ^-------^ SC2086 (info): Double quote 
to prevent globbing and word splitting.
   
   Did you mean:
     MODULE_TYPELIB_DIR_VAR_NAME="$(echo "${module}" | tr a-z- 
A-Z_)_TYPELIB_DIR"
   
   In c_glib/test/run-test.sh line 77:
   ${DEBUGGER} "${DEBUGGER_ARGS[@]}" "${RUBY}" ${test_dir}/run-test.rb "$@"
                                               ^---------^ SC2086 (info): 
Double quote to prevent globbing and word splitting.
   
   Did you mean:
   ${DEBUGGER} "${DEBUGGER_ARGS[@]}" "${RUBY}" "${test_dir}"/run-test.rb "$@"
   
   For more information:
     <https://www.shellcheck.net/wiki/SC2046> -- Quote this to prevent word 
splitt...
     <https://www.shellcheck.net/wiki/SC2164> -- Use 'cd ... || exit' or 'cd 
... |...
     <https://www.shellcheck.net/wiki/SC2086> -- Double quote to prevent 
globbing ...
   
   ```
   
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   
   ### What changes are included in this PR?
   - add missing double quotes(SC2046,SC2086)
   - Use cd ... || exit in case cd fails.(SC2164)
   
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   
   ### Are these changes tested?
   yes
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   ### Are there any user-facing changes?
   no
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please uncomment the line 
below and explain which changes are breaking.
   -->
   <!-- **This PR includes breaking changes to public APIs.** -->
   
   <!--
   Please uncomment the line below (and provide explanation) if the changes fix 
either (a) a security vulnerability, (b) a bug that caused incorrect or invalid 
data to be produced, or (c) a bug that causes a crash (even when the API 
contract is upheld). We use this to highlight fixes to issues that may affect 
users without their knowledge. For this reason, fixing bugs that cause errors 
don't count, since those are usually obvious.
   -->
   <!-- **This PR contains a "Critical Fix".** -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to