Skip to content

fix(core): skip unreachable wellknown sources instead of dropping all - #62578

Open
Tarquinen wants to merge 1 commit into
devfrom
wellknown-origin-skip
Open

Tarquinen wants to merge 1 commit into
devfrom
wellknown-origin-skip

Conversation

@Tarquinen

@Tarquinen Tarquinen commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

Issue for this PR

Closes #46187

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

If one well-known source is unreachable and has no cached manifest, loading every source fails, so all well-known integrations and their remote config disappear after a restart and login reports "Integration not found" for a healthy origin. Now an unreachable source is logged and skipped, on both startup and the periodic refresh, and the other sources load normally. Sources with a cached manifest still fall back to it as before.

How did you verify your code works?

Logged in to the example well-known server with an unresolvable origin added to the saved sources, in throwaway data dirs. On dev the healthy origin is "Integration not found"; on this branch it resolves. Added a regression test; typecheck and the well-known and config tests pass.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Added by the opencode bot (AI-generated).

Related: #59320

@opencodejr opencodejr Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I ran the #46187 repro script against both checkouts from source. On the base branch, adding an unresolvable origin to wellknown:sources makes login to the healthy example server fail with Integration not found. With this change it still resolves (Available: login). The new test fails on the base branch and passes here. The wellknown and config tests pass, and typecheck:tsc for packages/core passes.

Public API is unchanged: this only changes how WellKnown.load/refresh handle a source that fails and has no cached manifest.

No concerns.

Related: #59320

@Tarquinen
Tarquinen force-pushed the wellknown-origin-skip branch from fe28e0f to 22fed85 Compare November 8, 2026 12:39

@opencodejr opencodejr Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This push only rebases the branch onto the latest dev, and the change is the same as before. I re-ran the #46187 repro on the rebased branch. The healthy origin still resolves when an unreachable source is listed, while dev still reports Integration not found. The well-known tests and the packages/core type check (typecheck:tsc) pass. The public API is unchanged, and I have no new concerns.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

One unreachable well-known origin hides every other integration

1 participant