Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 84063b3 (merge ref)

App install/install

run 36816526513

Execution chains

12 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2729 · node]step: Install dependencies (lifecycle scripts execute here)
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1434260636[2084 · provjobd1434260636]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1459 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[558 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36816526513
Profile UUID01a0f5c8-469b-766f-9e88-3a65fc8b9e50
Commit SHA84063b3229bcae37439f482b2ad0e9100450fd99(merge ref)
Refrefs/pull/41/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.

Read the docs