Execution Profile

garnet-org/action

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

CI/build-and-verify

run 37303858900

Execution chains

8 destinations · 8 processes
  • systemd
    • hosted-compute-agent[2066 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2173 · Runner.Worker]
          • bash
            • node[2625 · node]step: Install dependencies
              • registry.npmjs.org104.16.7.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2593 · node]
            • api.github.com140.82.112.5:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2568741277[2086 · provjobd2568741277]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
    • systemd-resolved[498 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1478 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[722 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a10bd9-3bf6-7a2f-a5d0-ff87ef24a113
Refrefs/pull/180/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.