I’m assuming what you want is to get a list of all the crates owned by a specific user on crates.io programmatically. # Cargo.toml [dependencies] crates_io_api = "0.11" // src/main.rs use crates_io_api::{CratesQuery, SyncClient}; fn main() { let username = "HashiramaSenjuhari"; // See https://crates.io/policies#crawlers let client = SyncClient::new( "bot_agent (some way to contact you, the bot runner)", std::time::Duration::from_secs(1), ).unwrap(); let user = client.user(username).unwrap(); let query = CratesQuery::builder() .sort(crates_io_api::Sort::RecentUpdates) .user_id(user.id) .build(); let crates = client.crates(query).unwrap(); let on_page = crates.meta.total; println!("Found {on_page} crates by {username}:"); for krate in &crates.crates { println!("- crate {}", krate.name); } }

I'm doing simple, synchronous DNS AXFR requests using hickory_client. These are necessarily over TCP. What I've noticed is that sometimes, especially with large zones, the DNS server (BIND in this case) will log a connection reset after my program is finished. Here's a minimal example that demonstrates the issue: use anyhow::anyhow; use anyhow::Result; use hickory_client::client::{Client, SyncClient}; use hickory_client::op::DnsResponse; use hickory_client::rr::{DNSClass, Name, RecordType}; use hickory_client::tcp::TcpClientConnection; use std::net::SocketAddr; fn main() -> Result<()> { let address: SocketAddr = "127.0.0.1:53".parse()?; let conn = TcpClientConnection::new(address)?; let client = SyncClient::new(conn); let response: DnsResponse = client.query( &Name::from_utf8("example.com").unwrap(), DNSClass::IN, RecordType::AXFR, )?; if !response.contains_answer() { return Err(anyhow!("AXFR returned no answers: {response:?}")); } let answers = response.answers(); let answers = answers .iter() .filter(|rec| matches!(rec.record_type(), RecordType::A | RecordType::AAAA)); for record in answers { let rr_name = record.name().to_utf8(); let rr_data = match record.data() { Some(data) => data, None => continue, }; let rr_addr = match rr_data.ip_addr() { Some(addr) => addr, None => continue, }; println!("{} -> {}", rr_name, rr_addr); } Ok(()) } This works fine, but sometimes the name server reports that the connection was reset: 26-Nov-2024 02:30:56.328 xfer-out: info: client @0x7f6a2cda9010 127.0.0.1#33124 (example.com): transfer of 'example.com/IN': AXFR started (serial 2024111830) 26-Nov-2024 02:30:56.336 xfer-out: error: client @0x7f6a2cda9010 127.0.0.1#33124 (example.com): transfer of 'example.com/IN': send: connection reset I assume this is because the server tried to send some more data but my client had already closed the stream. I'd like to understand if I am doing something wrong here and how I could close the TCP connection gracefully. I feel like I am missing something obvious, because I am a Rust beginner, so I feel reluctant to join hickory-dns's Discord to ask about this.

Here added SyncClient class which will be base for our new sync engine. For now it can synchronize one immerhin store. Event emitter is shared with canvas directly to avoid indirection of iframe po...

Storage-agnostic core for the cloud_sync family. Defines StorageAdapter, SyncEngine, SyncClient, ManifestDiffer, and conflict resolution — shared by every backend adapter. Changelog excerpt: Initial release. Storage-agnostic core extracted from `drive_sync_flutter 1.2.0`. - `StorageAdapter`: 5-method abstract interface (`ensureFolder`, `listFiles`, `uploadFile`, `downloadFile`, `deleteFile`) - `SyncEngine`: orchestrates manifest diffing, conflict resolution, and file transfer - `ManifestDiffer`: compares two sync manifests (added / modified / deleted / unchanged) - `ConflictResolver`: four strategies — `newerWins`, `localWins`, `remoteWins`, `askUser` - `SyncClient`: high-level bid[...]

Google Drive adapter for the cloud_sync family. Supports drive, drive.file, and drive.appdata scopes. Implements StorageAdapter so it plugs directly into SyncClient. Changelog excerpt: Initial release as part of the `cloud_sync`family. Behavior ported from `drive_sync_flutter 1.2.0`. - `DriveAdapter`(renamed from `GoogleDriveAdapter`) implements `StorageAdapter`from `cloud_sync_core` - Three factory constructors for OAuth scope selection: - `DriveAdapter.userDrive(basePath:, subPath:)`— full `drive`scope - `DriveAdapter.appFiles(folderName:, subPath:)`— `drive.file`scope - `DriveAdapter.appData(subPath:)`— `drive.appdata`scope - `DriveAuthClient`— `http.BaseClient`wra[...]