Force IPv4 for knowledge-search indexer DB connections on GitHub Actions

[Copilot]

knowledge-search:index fails on ubuntu-latest because the Supabase hostname can resolve to IPv6, while the runner has no outbound IPv6 route (ENETUNREACH). This change forces IPv4 address selection for the indexer’s Postgres connection.

• Connection behavior update (scripts/knowledge-search/embed-docs.mjs)

  • Updated postgres() client options to include family: 4.
  • Kept existing SSL behavior unchanged.

• Why this addresses the failure

  • postgres.js now resolves/uses IPv4 for the DB socket, avoiding unreachable IPv6 paths on the GitHub-hosted runner.

const sql = postgres(env.SUPABASE_DB_URL, {
  ssl: env.SUPABASE_DB_SSL === "disable" ? false : "require",
  family: 4,
});

Original prompt

Problem

The knowledge-search:index job fails immediately with a network error on GitHub Actions runners:

Error: connect ENETUNREACH 2a05:d014:8ef:5900:cb94:a6b2:c8f1:2a45:5432

The Supabase hostname resolves to an IPv6 address, but ubuntu-latest GitHub Actions runners do not have outbound IPv6 connectivity, so the connection is unreachable.

Fix

In scripts/knowledge-search/embed-docs.mjs, add family: 4 to the postgres() connection options to force IPv4 DNS resolution:

// Before (line 27)
const sql = postgres(env.SUPABASE_DB_URL, {ssl: env.SUPABASE_DB_SSL === "disable" ? false : "require"});

// After
const sql = postgres(env.SUPABASE_DB_URL, {
  ssl: env.SUPABASE_DB_SSL === "disable" ? false : "require",
  family: 4,
});

The family: 4 option is supported by postgres.js and instructs the underlying Node.js net module to resolve the hostname to an IPv4 address only, bypassing the unreachable IPv6 address.

No other files need to be changed.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Please find a solution for this failing job. Use the logs, job definition, and any referenced files where the failure occurred. Keep your response focused on the solution and include code suggestions when appropriate.

Assistant: I'll grab the job logs right away!

Assistant: ## Problem

The job fails immediately with a network error trying to connect to the Supabase PostgreSQL database on port 5432:

Error: connect ENETUNREACH 2a05:d014:8ef:5900:cb94:a6b2:c8f1:2a45:5432

The address 2a05:d014:... is IPv6. GitHub Actions ubuntu-latest runners do not have outbound IPv6 connectivity, so the connection is unreachable. The postgres client is resolving the Supabase hostname to an IPv6 address and failing before even attempting IPv4.

Solution

Force the postgres client to use IPv4 by passing family: 4 in the connection options. In scripts/knowledge-search/embed-docs.mjs, update line 27:

// Before
const sql = postgres(env.SUPABASE_DB_URL, {ssl: env.SUPABASE_DB_SSL === "disable" ? false : "require"});

// After
const sql = postgres(env.SUPABASE_DB_URL, {
  ssl: env.SUPABASE_DB_SSL === "disable" ? false : "require",
  family: 4,
});

The family: 4 option is supported by postgres.js and instructs the underlying Node.js net module to resolve the hostname to an IPv4 address only, bypassing the IPv6 address that the GitHub Actions runner can't reach.

User: Open PR please

Assistant: We're waiting for your response to the tool confirmation dialog to proceed with creating the pull request.

This pull request was created from Copilot chat.

[cloudflare-workers-and-pages]

Deploying zsh with    Cloudflare Pages

Latest commit:	6bea222
Status:	✅  Deploy successful!
Preview URL:	https://c2024bea.zsh.pages.dev
Branch Preview URL:	https://copilot-fix-knowledge-search.zsh.pages.dev

View logs

[Copilot]

Pull request overview

This PR addresses a CI reliability issue where the knowledge-search indexer fails on GitHub Actions runners due to Supabase resolving to an IPv6 address while ubuntu-latest lacks outbound IPv6 routing.

Changes:

• Forces IPv4 DNS selection for the indexer’s Postgres connection by passing family: 4 to postgres() in the embedding/indexing script.