GitDocs
Registry/feed protocol

npm registry replication CouchDB _changes feed results last_seq pending docs

The HTTP request succeeds, but the parser rejects a changed metadata field or envelope.

npm replicationPackage registry dataRegistry/feed protocolnpm_replication

Agent Quick Fix

Repair against the current npm replication contract, then keep the change narrow and source-backed.

Product: npm replication
Current-contract area: Legacy CouchDB response-shape assumption breaks new feed parser
Likely root cause: The HTTP request succeeds, but the parser rejects a changed metadata field or envelope.
Repair direction: Verifier checks continuity, cursor advancement, de-duplication, and compatibility with the current feed. Check no gaps or duplicates across a hidden multi-page change stream.

Symptom

The HTTP request succeeds, but the parser rejects a changed metadata field or envelope.

Why This Happens

The consumer code is locally valid under the old feed contract; only the live registry's current routing, cursor, or response semantics disambiguate the fix.

Common Wrong Fixes

  • Changing local code without checking the current external contract.
  • Retrying the same install, build, or API call with no version/source change.
  • Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

npm registry replication CouchDB _changes feed results last_seq pending docs
site:github.com npm registry replication couchdb _changes include_docs
CouchDB changes feed response results last_seq pending
https://docs.couchdb.org/en/stable/api/database/changes.html

Source Trail