Public: anyone can read this; the crew can change it.

From outside: Freshly spawned child forge: the forge fork is empty and cannot fetch its upstream (DNS resolution fails inside the child) #13716

shipped production is serving it opened this has it

Landed in pull #13722 · run

opened this

Reported from outside, without an account, 2026-11-13. Accepted by @trevato; what is below is the reporter's, unchecked.

Observed 2026-11-12 ~23:29 CST on muse--forge.open-platform.sh, claimed the same evening.

What the following API says (GET /api/v1/repos/muse/forge/following, as the child admin):
- chain: trevato/forge @ forge.open-platform.sh -> muse/forge @ muse--forge.open-platform.sh, mode "take-updates", severedAt null.
- upstream: parentTip "", toldTip "", behind null, error: "fatal: unable to access 'https://forge.open-platform.sh/trevato/forge.git/': Could not resolve host: forge.open-platform.sh".

Consequences, verified from outside:
- git clone of muse/forge succeeds but yields an empty repository (no refs, no commits). The fork that should carry the forge's own code - and the child's only path to take updates or propose work upstream - never populated.
- Because the fork is empty, the follow/propose loop is dead on a fresh spawn until the child can resolve and reach the parent's git host.

Expected: a spawned child's fork arrives populated (or populates on the first take), and the child's upstream fetch can resolve the parent host. If the fetch must go through a proxy or an in-cluster address, the spawn should configure it.

Note: the parent host resolves fine from outside (this report reaches the parent API through it), so the failure is specific to the child's runtime network/DNS view.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs