alibaba/java-dns-cache-manipulator

Can't follow non-constant source. Use a directive to specify location.

Problematic code:

. "$(find_install_dir)/lib.sh"

Correct code:

# shellcheck source=src/lib.sh
. "$(find_install_dir)/lib.sh"

Rationale:

ShellCheck is not able to include sourced files from paths that are determined at runtime. The file will not be read, potentially resulting in warnings about unassigned variables and similar.

Use a [[Directive]] to point shellcheck to a fixed location it can read instead.

Exceptions:

If you don't care that ShellCheck is unable to account for the file, specify # shellcheck source=/dev/null.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

This directive is unknown. It will be ignored.

Problematic code:

# shellcheck foobar=baz
echo "Hello World"

Correct code:

Depends on your intention.

Rationale:

ShellCheck doesn't recognize the [[directive]] you're trying to use in a # shellcheck comment. See the [[Directive]]s page for supported directives.

It could be misspelled, or you could be using an older version of shellcheck that doesn't support it yet.

Exceptions:

None. If you wish to ignore this warning and continue without it, you need version 0.4.5 (commit 88c56ec) or later and a command grouping:

# Ignore an unrecognized directive in 0.4.5 or later:
# shellcheck disable=SC1107
{
  # shellcheck unrecognized=directive
  echo "Hello World"
}

Before 0.4.5, unrecognized directives are considered parse errors.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

This \o will be a regular 'o' in this context.

Problematic code:

# Want literal backslash
echo Yay \o/

# Want linefeed
greeting=Hello\nWorld

# Want other characters
carriagereturn=\r

Correct code:

echo 'Yay \o/'

greeting='Hello
World'

carriagereturn=$(printf '\r')

Rationale:

You have escaped something that has no special meaning when escaped. The backslash will be simply be ignored.

If the backslash was supposed to be literal, single quote or escape it.

If you wanted it to expand to something, rewrite the expression. For linefeeds (\n), put them literally in quotes. For other characters, use POSIX printf or bash/ksh $'...'.

Exceptions

None. ShellCheck (as of 2017-07-03, commit 31bb02d6) will not warn when the first letter of a command is unnecessarily escaped, as this is frequently used to suppress aliases interactively.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

This directive is unknown. It will be ignored.

Problematic code:

# shellcheck foobar=baz
echo "Hello World"

Correct code:

Depends on your intention.

Rationale:

ShellCheck doesn't recognize the [[directive]] you're trying to use in a # shellcheck comment. See the [[Directive]]s page for supported directives.

It could be misspelled, or you could be using an older version of shellcheck that doesn't support it yet.

Exceptions:

None. If you wish to ignore this warning and continue without it, you need version 0.4.5 (commit 88c56ec) or later and a command grouping:

# Ignore an unrecognized directive in 0.4.5 or later:
# shellcheck disable=SC1107
{
  # shellcheck unrecognized=directive
  echo "Hello World"
}

Before 0.4.5, unrecognized directives are considered parse errors.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

This directive is unknown. It will be ignored.

Problematic code:

# shellcheck foobar=baz
echo "Hello World"

Correct code:

Depends on your intention.

Rationale:

ShellCheck doesn't recognize the [[directive]] you're trying to use in a # shellcheck comment. See the [[Directive]]s page for supported directives.

It could be misspelled, or you could be using an older version of shellcheck that doesn't support it yet.

Exceptions:

None. If you wish to ignore this warning and continue without it, you need version 0.4.5 (commit 88c56ec) or later and a command grouping:

# Ignore an unrecognized directive in 0.4.5 or later:
# shellcheck disable=SC1107
{
  # shellcheck unrecognized=directive
  echo "Hello World"
}

Before 0.4.5, unrecognized directives are considered parse errors.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

Not following: (error message here)

Reasons include: file not found, no permissions, not included on the command line, not allowing shellcheck to follow files with -x, etc.

Problematic code:

source somefile

Correct code:

# shellcheck disable=SC1091
source somefile

Rationale:

ShellCheck, for whichever reason, is not able to access the source file.

This could be because you did not include it on the command line, did not use shellcheck -x to allow following other files, don't have permissions or a variety of other problems.

Feel free to ignore the error with a [[directive]].

Exceptions:

If you're fine with it, ignore the message with a [[directive]].

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

This \o will be a regular 'o' in this context.

Problematic code:

# Want literal backslash
echo Yay \o/

# Want linefeed
greeting=Hello\nWorld

# Want other characters
carriagereturn=\r

Correct code:

echo 'Yay \o/'

greeting='Hello
World'

carriagereturn=$(printf '\r')

Rationale:

You have escaped something that has no special meaning when escaped. The backslash will be simply be ignored.

If the backslash was supposed to be literal, single quote or escape it.

If you wanted it to expand to something, rewrite the expression. For linefeeds (\n), put them literally in quotes. For other characters, use POSIX printf or bash/ksh $'...'.

Exceptions

None. ShellCheck (as of 2017-07-03, commit 31bb02d6) will not warn when the first letter of a command is unnecessarily escaped, as this is frequently used to suppress aliases interactively.

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.

Not following: (error message here)

Reasons include: file not found, no permissions, not included on the command line, not allowing shellcheck to follow files with -x, etc.

Problematic code:

source somefile

Correct code:

# shellcheck disable=SC1091
source somefile

Rationale:

ShellCheck, for whichever reason, is not able to access the source file.

This could be because you did not include it on the command line, did not use shellcheck -x to allow following other files, don't have permissions or a variety of other problems.

Feel free to ignore the error with a [[directive]].

Exceptions:

If you're fine with it, ignore the message with a [[directive]].

Notice

Original content from the ShellCheck https://github.com/koalaman/shellcheck/wiki.