"SIGTERMandSIGINThave default handlers on non-Windows platforms that resets the terminal mode before exiting with code128 + signal number. If one of these signals has a listener installed, its default behavior will be removed (Node.js will no longer exit)." According to that, I am not sure...
shortMessage: 'Command failed with exit code 128: git ls-remote --heads https://github.com/my/repo', command: 'git ls-remote --heads https://github.com/my/repo', exitCode: 128, signal: undefined, signalDescription: undefined, stdout: '', stderr: "fatal: could not read Username for...
return sprintf(__("fatal: command '%s' died with exit code %d"), @sprintf_args); } sub system_or_die { my $msg = system_or_msg(@_); die $msg if $msg; } sub do_edit { if (!defined($editor)) { $editor = Git::command_oneline('var', 'GIT_EDITOR'); } ...
If you encounter a problem and can't enable C99 * support with your compiler (such as with "-std=gnu99") and don't have access * to one with this support, such as GCC or Clang, you can remove this #if * directive, but please report the details of your system to ...
Try a normalkill.if [ $? != 0 ]; then if [ ! -z "$CATALINA_PID" ]; then echo "The stop command failed. Attempting to signal the process to stop through OS signal." kill -15 `cat "$CATALINA_PID"` >/dev/null 2>&1
{"error":"signal: killed","level":"warning","msg":"exited","supervisor.args":["bundle","exec","bin/ruby-cd","/var/opt/gitlab/gitaly","/opt/gitlab/embedded/service/gitaly-ruby/bin/gitaly-ruby","2983","/var/opt/gitlab/gitaly/internal_sockets/ruby.0"],"supervisor.name":"gitaly-...
Otherwise, the program is run. If it terminates regularly, its exit code is returned. No diagnostic is printed, even if the exit code is non-zero. If the program terminated due to a signal, then the return value is the signal number + 128, ie. the same value that a POSIX shell’s...
Otherwise, the program is run. If it terminates regularly, its exit code is returned. No diagnostic is printed, even if the exit code is non-zero. If the program terminated due to a signal, then the return value is the signal number + 128, ie. the same value that a POSIX shell’s...
GitLab Why GitLab Pricing Explore Sign in Get free trial Primary navigation Search or go to… Project Linux Kernel Manage Plan Code Build Deploy Releases Package registry Container registry Model registry Operate Monitor Analyze Help XanMod...
* GNU diff puts epoch there to signal a creation/deletion event. Is * this such a timestamp? */ static int has_epoch_timestamp(const char *nameline) { /* * We are only interested in epoch timestamp; any non-zero * fraction cannot be one, hence "(\.0+)?" in the regexp below...