Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit e042b53 (merge ref)

App install/install

run 36820479602

Execution chains

12 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2164 · Runner.Worker]
          • bash
            • node[2608 · 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)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3306201021[2077 · provjobd3306201021]
          • 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
    • systemd-resolved[502 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1504 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820479602
Profile UUID01a0f5f6-9025-7c53-bd30-8f6e79f54193
Commit SHAe042b530861c8b7f65f878f3fd96003d4f8342f7(merge ref)
Refrefs/pull/76/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