Skip to main content

Module repo

Module repo 

Source

EnumsΒ§

Occupied πŸ”’
What a route does about a record key that is already taken.

FunctionsΒ§

apply_writes πŸ”’
POST /xrpc/com.atproto.repo.applyWrites
charge_write πŸ”’
Spends ops write operations and bytes request bytes of did’s share of AppState::write_meter, or refuses with 429 RateLimitExceeded.
check_write_not_halted πŸ”’
The shared gate on every com.atproto.repo.* write.
create_record πŸ”’
POST /xrpc/com.atproto.repo.createRecord
delete_record πŸ”’
POST /xrpc/com.atproto.repo.deleteRecord
describe_repo πŸ”’
GET /xrpc/com.atproto.repo.describeRepo
get_record πŸ”’
GET /xrpc/com.atproto.repo.getRecord
is_swap_failure πŸ”’
Whether a refusal was a record-level compare-and-swap failing.
list_records πŸ”’
GET /xrpc/com.atproto.repo.listRecords
meter_write πŸ”’
charge_write, against meter, refusing as the store refuses: the admission charge a record write carries into it.
put_record πŸ”’
POST /xrpc/com.atproto.repo.putRecord
refused_write πŸ”’
A store’s refusal of a write, as the caller hears it.
require_account_capacity πŸ”’
Refuses a new account once this deployment already holds AppState::max_accounts of them; see crate::tree::create_account.
require_lifecycle πŸ”’
The one place this server’s own lifecycle refuses a request.
require_record_writes πŸ”’
The lifecycle’s half of check_write_not_halted, alone.
require_writable_repo πŸ”’
docs/write-pipeline.md’s stage 3, run at the earliest moment a route can run it: the instant the request envelope names a repository.
to_batch_op πŸ”’
Converts one wire-level write into the shape Registry::apply_writes takes, dropping nothing: the collection, key and value every variant carries reach the registry exactly as the caller sent them.
unnameable_record πŸ”’
The 500 for a stored record the data model cannot name.
write_record πŸ”’
The write both createRecord and putRecord perform.
write_result πŸ”’
One batch outcome, on the wire β€” told apart as a create or an update by the operation that produced it, since didbot_pds::BatchOutcome itself does not carry that distinction.