When options.timeout is not set, some commands times-out with:
[Linter] Error running ShellCheck Error: Process execution timed out
at /home/username/.atom/packages/linter-shellcheck/node_modules/sb-exec/lib/index.js:89
Expected behavior
When options.timeout is not set:
Use a reasonable default timeout value other than 0.
Have the default value written back to config.
Eventually, report an average-human-readable explicit message, that the option is not set and it uses the default value.
The time, in milliseconds (thousandths of a second), the timer should wait before the specified function or code is executed. __If this parameter is omitted, a value of 0 is used, meaning execute "immediately", or more accurately, the next event cycle___. Note that in either case, the actual delay may be longer than intended; see Reasons for delays longer than specified below.
Issue details
When
options.timeout
is not set, some commands times-out with:Expected behavior
When
options.timeout
is not set:Notes
The MDN/
WindowOrWorkerGlobalScope.setTimeout()
, Parameters documentations says that the default value is0
milliseconds:Related issues