Hi! We are seeing a case where some CLI-created sh.tangled.repo.pull records exist in PDS/Constellation, but AppView never assigns them a /pulls/N page. Could someone with AppView logs/DB access help check what the pull ingester did for these records?
Repository:
- https://tangled.org/onev.cat/tang
- repo DID:
did:plc:vglueuiqgjehmkqpjloszu2q - pull author DID:
did:plc:kl2ejrmz5zmxnno3ll4luz76
Records that are present in PDS/Constellation but not projected by AppView:
at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.pull/3mm2mljaqtw22at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.pull/3mm2ojezxm622
Both records target the same repo DID and use branch-based pull requests:
target.repo = did:plc:vglueuiqgjehmkqpjloszu2qtarget.branch = mainsource.repo = did:plc:vglueuiqgjehmkqpjloszu2q- first source branch:
fix/appview-number-resolution - second source branch:
e2e-identifier-fix-copy-20260518-0028
The patch blob for 3mm2mljaqtw22 is:
- CID:
bafkreiairtrk7ow634jlwe7ykioy5gckn2nomlupbhsz46lszodwvvb7zi - size:
13123 - MIME:
application/gzip
We verified from the same PDS endpoint that the blob downloads with HTTP 200, content-length matches, gzip -t passes, and the expanded patch applies cleanly with git apply --check against main.
For comparison, these CLI-created pull records on the same repo did project correctly:
at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.pull/3mm2nt6ojvm22-> https://tangled.org/onev.cat/tang/pulls/5/round/0at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.pull/3mm2nyt5wh222-> https://tangled.org/onev.cat/tang/pulls/6/round/0
Also, a web-created PR for the same patch appears as:
- https://tangled.org/onev.cat/tang/pulls/4/round/0
- record:
at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.pull/3mm2nn7efc622
That web-created PR uses the same patch blob CID as 3mm2mljaqtw22, but it was created through AppView, so it may have gone through the direct web create path that writes AppView DB rows immediately rather than relying on the firehose pull ingester.
Could you please check AppView logs for handler=ingestPull around these rkeys?
did=did:plc:kl2ejrmz5zmxnno3ll4luz76 rkey=3mm2mljaqtw22did=did:plc:kl2ejrmz5zmxnno3ll4luz76 rkey=3mm2ojezxm622
The main question is whether ingestPull returned an error and advanced the cursor anyway. If so, the error message should tell us whether the failure is in blob download, gzip extraction, patch parsing, validation, or DB insertion.
Thanks!
thanks for opening this issue, seems like a bug on our end, will investigate.