In reply to @kasbah:matrix.org
i can just delete the hdd of the staging servers, right? even abdo-dev?

Abdulrhmn Ghanem:

I like Docker Compose but you need to be aware of some limitations. For example, healthchecks are allowed in the docker-compose.yml file but Docker Compose will never check for them periodically. This was supposed to be something just for Docker Swarm, which uses the same format. Devs don’t want to introduce healthcheck into Docker itself (and Docker Compose doesn’t add any daemon for that either).

https://lobste.rs/s/wdqpcw/just_paying_figma_15_month_because#c_tesbpl

In reply to @kasbah:matrix.org

Abdulrhmn Ghanem:

I like Docker Compose but you need to be aware of some limitations. For example, healthchecks are allowed in the docker-compose.yml file but Docker Compose will never check for them periodically. This was supposed to be something just for Docker Swarm, which uses the same format. Devs don’t want to introduce healthcheck into Docker itself (and Docker Compose doesn’t add any daemon for that either).

https://lobste.rs/s/wdqpcw/just_paying_figma_15_month_because#c_tesbpl

Abdulrhmn Ghanem: I think the default is for the mirrors to update every 10m. The issue on review seems to be this making the processor crash:

🚀 Kitspace processor service is running.
https://partinfo.kitspace.org/graphql health check passed
Acquired sync lock for  /gitea-data/git/repositories/jana-marie/usb-led-otter.git
Pulling updates for /gitea-data/git/repositories/jana-marie/usb-led-otter.git
node:internal/errors:857
  const err = new Error(message);
              ^

Error: Command failed: cd /data/checkout/Jana-Marie/USB-LED-Otter && git pull
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket.<anonymous> (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:301:12) {
  code: 128,
  killed: false,
  signal: null,
  cmd: 'cd /data/checkout/Jana-Marie/USB-LED-Otter && git pull',
  stdout: '',
  stderr: 'fatal: not a git repository (or any parent up to mount point /)\n' +
    'Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).\n'
}

In reply to @kasbah:matrix.org

Abdulrhmn Ghanem: I think the default is for the mirrors to update every 10m. The issue on review seems to be this making the processor crash:

🚀 Kitspace processor service is running.
https://partinfo.kitspace.org/graphql health check passed
Acquired sync lock for  /gitea-data/git/repositories/jana-marie/usb-led-otter.git
Pulling updates for /gitea-data/git/repositories/jana-marie/usb-led-otter.git
node:internal/errors:857
  const err = new Error(message);
              ^

Error: Command failed: cd /data/checkout/Jana-Marie/USB-LED-Otter && git pull
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket.<anonymous> (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:301:12) {
  code: 128,
  killed: false,
  signal: null,
  cmd: 'cd /data/checkout/Jana-Marie/USB-LED-Otter && git pull',
  stdout: '',
  stderr: 'fatal: not a git repository (or any parent up to mount point /)\n' +
    'Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).\n'
}