Our Personal Data Server from scratch! tranquil.farm
oauth atproto pds rust postgresql objectstorage fun

Lexicon schema validation isn't generic #35

open opened by test.rainy.pet edited

Attempting to post with "Allow quote posts" set to off in social-app will fail and result in a "Lexicon not found: lex:app.bsky.feed.postgate" message appearing at the top of the composer. Unclear what the cause is, last few logs after the attempt are:

2026-03-08T15:09:28.581715Z  INFO tranquil_pds::api::proxy: Proxying GET request to https://api.bsky.app/xrpc/app.bsky.actor.getProfile?actor=did%3Aplc%3Abpu2pz4q53tbdusav2je377x
2026-03-08T15:09:28.581894Z  INFO tranquil_pds::api::proxy: Proxying GET request to https://api.bsky.app/xrpc/app.bsky.actor.getProfile?actor=did%3Aplc%3Atzrpqyerzt37pyj54hh52xrz
2026-03-08T15:09:29.503903Z  INFO tranquil_pds::api::repo::record::batch: apply_writes called: repo=did:plc:bpu2pz4q53tbdusav2je377x, writes=3
2026-03-08T15:09:29.577748Z  INFO tranquil_pds::api::proxy: Proxying GET request to https://api.bsky.app/xrpc/app.bsky.draft.getDrafts

with the following response on the client:

{
    "error": "InvalidRecord",
    "message": "Lexicon not found: lex:app.bsky.feed.postgate"
}

Right now it appears tranquil hardcodes some validations of records and fails otherwise if validate is passed and it doesn't recognize the lexicon (I assume)

that sure is whats happening ... validation is hard coded and hand written rn ...

we'll get that sorted. maybe change the issue name to "lexicon schema validation isnt generic" or something? just so we can keep track of whats going on here

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:bpu2pz4q53tbdusav2je377x/sh.tangled.repo.issue/3mgkmxziqg622