Refresh-refcache PR fix
Follow these steps to resolve non-2XX static/refcache.json entries in the
otelbot/refcache-refresh PR. This process may involve updating or removing
dead links on the site, then refreshing the refcache again until no non-2XX
entries remain.
Preparation
These steps assume you have a local clone of the repository with the upstream
remote configured to point to the main repository. Run these steps locally from
the repository root.
Determine the PR associated with upstream
otelbot/refcache-refresh.If none exists, stop.
If a local
otelbot/refcache-refreshbranch already exists and contains commits that are not inupstream/otelbot/refcache-refresh, back them up or stop before resetting anything.Check out the PR branch with
gh pr checkout <num>. If that fails because the local branch has diverged and you have already backed up any local-only commits, realign it with upstream:git fetch upstream git checkout otelbot/refcache-refresh git reset --hard upstream/otelbot/refcache-refreshIf any content modules are out of date, run
npm run get:submodule.
Resolve non-2XX entries
Run
./scripts/double-check-refcache-4XX.mjsto retry transient 4XX failures and updatestatic/refcache.json.Scan
static/refcache.jsonfor remaining non-2XX statuses.If none remain, commit and push any changed files (only
static/refcache.jsonshould have changed) toupstream/otelbot/refcache-refresh, then stop.List remaining non-2XX URLs and their statuses:
jq -r 'to_entries[] | select(.value.StatusCode < 200 or .value.StatusCode >= 300) | "\(.key) \(.value.StatusCode)"' \ static/refcache.jsonFor each remaining status, fix or remove the source link that produced it:
- For a 404, identify the site pages that refer to the dead URL and update or remove that link.
- For any other non-2XX status, inspect it manually and update or remove the source link as needed before continuing.
Run
npm run fix:refcacheto refreshstatic/refcache.jsonafter those source-link changes, then repeat the steps in this section until no non-2XX statuses remain.