Public Build Artifact: Linux 10102120188

restored certifi depend payload

This commit simply adds-back the certifi file from the previous commit by executing this in the sandbox

  user@buskill:~/sandbox/buskill-app/build/deps$ git checkout 35fef0d63f3f8ea0ec6ea8edc68e40965ec3c991 certifi-2020.6.20-py2.py3-none-any.whl
  Updated 1 path from e7d0a4a
  user@buskill:~/sandbox/buskill-app/build/deps$

This was done to see if it fixes the recent build issues from the last commit
 * https://github.com/BusKill/buskill-app/commit/19d14f62d0ba94c148094d454d0f41732d9a71ff
 * https://github.com/BusKill/buskill-app/issues/24#issuecomment-2251459209

Public Build Artifact: Windows 10084283950

remove dependencies payload files

This commit removes the dependencies for this project, which were since moved to a distinct repo to prevent *this* code repo from further ballooning in size.

For more info, see:

 * https://github.com/BusKill/buskill-app/issues/2
 * https://github.com/BusKill/buskill-app/issues/24#issuecomment-2248930362

Hopefully all builds will succeed, and then I can close issue #24 above.

Public Build Artifact: Mac 10084283950

remove dependencies payload files

This commit removes the dependencies for this project, which were since moved to a distinct repo to prevent *this* code repo from further ballooning in size.

For more info, see:

 * https://github.com/BusKill/buskill-app/issues/2
 * https://github.com/BusKill/buskill-app/issues/24#issuecomment-2248930362

Hopefully all builds will succeed, and then I can close issue #24 above.

Public Build Artifact: Linux 10084283950

remove dependencies payload files

This commit removes the dependencies for this project, which were since moved to a distinct repo to prevent *this* code repo from further ballooning in size.

For more info, see:

 * https://github.com/BusKill/buskill-app/issues/2
 * https://github.com/BusKill/buskill-app/issues/24#issuecomment-2248930362

Hopefully all builds will succeed, and then I can close issue #24 above.

Public Build Artifact: Windows 10084066193

attempt to fix clone errors

This commit updates the macos build script to clone the buskill deps repo using a depth of 1 and without tags, per:

 * https://serverfault.com/questions/1056419/git-wsl2-ssh-unexpected-disconnect-while-reading-sideband-packet

I'm doing this because I keep getting errors on the clone when attempting to run the build script on our mac mini

  + git clone https://github.com/BusKill/buskill-app-deps.git
  Cloning into 'buskill-app-deps'...
  error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
  error: 4973 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  fatal: early EOF
  fatal: fetch-pack: invalid index-pack output

Public Build Artifact: Mac 10084066193

attempt to fix clone errors

This commit updates the macos build script to clone the buskill deps repo using a depth of 1 and without tags, per:

 * https://serverfault.com/questions/1056419/git-wsl2-ssh-unexpected-disconnect-while-reading-sideband-packet

I'm doing this because I keep getting errors on the clone when attempting to run the build script on our mac mini

  + git clone https://github.com/BusKill/buskill-app-deps.git
  Cloning into 'buskill-app-deps'...
  error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
  error: 4973 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  fatal: early EOF
  fatal: fetch-pack: invalid index-pack output

Public Build Artifact: Linux 10084066193

attempt to fix clone errors

This commit updates the macos build script to clone the buskill deps repo using a depth of 1 and without tags, per:

 * https://serverfault.com/questions/1056419/git-wsl2-ssh-unexpected-disconnect-while-reading-sideband-packet

I'm doing this because I keep getting errors on the clone when attempting to run the build script on our mac mini

  + git clone https://github.com/BusKill/buskill-app-deps.git
  Cloning into 'buskill-app-deps'...
  error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
  error: 4973 bytes of body are still expected
  fetch-pack: unexpected disconnect while reading sideband packet
  fatal: early EOF
  fatal: fetch-pack: invalid index-pack output

Public Build Artifact: Windows 10069647580

improve set_trigger() fails

The last commit was successfully able to catch the failure to spawn the root_child process on setting the trigger to 'self-destruct' if the mode (permissions) on the root_child_process don't meet our security needs.

This commit improves the error message, and it also makes sure to revert-back the trigger to the old_trigger. Otherwise, it still tells the user that the trigger is 'soft-shutdown, even though that's impossible.

I probably should add something to the arm/disarm toggle that checks to see if the root_child is still running. something like a ping/pong "are you still alive?" test? If that fails, then we really should tell the user rather than letting them think that buskill is successfully armed.

Public Build Artifact: Mac 10069647580

improve set_trigger() fails

The last commit was successfully able to catch the failure to spawn the root_child process on setting the trigger to 'self-destruct' if the mode (permissions) on the root_child_process don't meet our security needs.

This commit improves the error message, and it also makes sure to revert-back the trigger to the old_trigger. Otherwise, it still tells the user that the trigger is 'soft-shutdown, even though that's impossible.

I probably should add something to the arm/disarm toggle that checks to see if the root_child is still running. something like a ping/pong "are you still alive?" test? If that fails, then we really should tell the user rather than letting them think that buskill is successfully armed.

Public Build Artifact: Linux 10069647580

improve set_trigger() fails

The last commit was successfully able to catch the failure to spawn the root_child process on setting the trigger to 'self-destruct' if the mode (permissions) on the root_child_process don't meet our security needs.

This commit improves the error message, and it also makes sure to revert-back the trigger to the old_trigger. Otherwise, it still tells the user that the trigger is 'soft-shutdown, even though that's impossible.

I probably should add something to the arm/disarm toggle that checks to see if the root_child is still running. something like a ping/pong "are you still alive?" test? If that fails, then we really should tell the user rather than letting them think that buskill is successfully armed.