docs: English Models & Pricing page unreachable upstream (serves fallback shell) - #9
Open
github-actions[bot] wants to merge 1 commit into
Open
docs: English Models & Pricing page unreachable upstream (serves fallback shell)#9github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…back shell) The English `Models & Pricing` page — the most developer-critical page in the mirror, and the one the high-signal criteria names first (pricing, model versions, context/output limits) — is no longer being served by upstream. `https://api-docs.deepseek.com/quick_start/pricing` returns HTTP 200 but with the SPA shell carrying the homepage article ("Your First API Call", canonical → `https://api-docs.deepseek.com/`), so this fetch recorded a fallback-shell error instead of the page title. The mirror's `content/en/quick_start/pricing.md` content is untouched (last good fetch 2026-08-08), but the manifest now flags that it can no longer be refreshed — meaning the mirror will silently go stale on pricing/model/limit changes until upstream recovers or the fetcher's source registry is repointed. This is fetch-health metadata rather than a content diff, but a human should look: the pricing page is exactly where a missed upstream change (new model version, price, or limit) would cost developers. - The en pricing manifest entry flipped from `"title": "Models & Pricing"` to a fallback-shell error; only `.metadata.json` changed in the tree — no content files. - The breakage is en-locale-specific: `/zh-cn/quick_start/pricing` still serves correctly (doc-id `quick_start/pricing`, title "模型 & 价格"). - The URL is still present in the en sitemap and the homepage nav still links to it, so the doc wasn't removed or renamed — upstream is simply serving the wrong article for the path. - This is now the second en page serving a fallback shell (`en/news/news250120.md` is still down), suggesting a possible broader en-site serving/routing issue rather than a one-off page move.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The English
Models & Pricingpage — the most developer-critical page in the mirror, and the one the high-signal criteria names first (pricing, model versions, context/output limits) — is no longer being served by upstream.https://api-docs.deepseek.com/quick_start/pricingreturns HTTP 200 but with the SPA shell carrying the homepage article ("Your First API Call", canonical →https://api-docs.deepseek.com/), so this fetch recorded a fallback-shell error instead of the page title. The mirror'scontent/en/quick_start/pricing.mdcontent is untouched (last good fetch 2026-08-08), but the manifest now flags that it can no longer be refreshed — meaning the mirror will silently go stale on pricing/model/limit changes until upstream recovers or the fetcher's source registry is repointed. This is fetch-health metadata rather than a content diff, but a human should look: the pricing page is exactly where a missed upstream change (new model version, price, or limit) would cost developers."title": "Models & Pricing"to a fallback-shell error; only.metadata.jsonchanged in the tree — no content files./zh-cn/quick_start/pricingstill serves correctly (doc-idquick_start/pricing, title "模型 & 价格").en/news/news250120.mdis still down), suggesting a possible broader en-site serving/routing issue rather than a one-off page move.