We've got quite a few fails because of a failure to check /xrpc/com.atproto.sync.getRepoState, which seems to mostly be when we hit cloudflare errors. We should handle these as HTTP errors instead of crashing the JSON parser
Parakeet is a Rust-based Bluesky AppServer aiming to implement most of the functionality required to support the Bluesky client
appview
atproto
bluesky
rust
appserver
Handle Cloudflare errors #16
closed
opened by
mia.omg.lol
Okay actually realised we weren't handling 5xx range errors at all, so now we do, not just the CF ones.