chore: cargo +nightly fmt

Author: coriolinus

crypto/src/ephemeral.rs

@@ -111,7 +111,8 @@ pub(crate) async fn generate_history_secret(ciphersuite: Ciphersuite) -> Result<
         .await
         .map_err(MlsError::wrap("encapsulating key package"))?;
 
-    // we don't need to finish the transaction here--the point of the ephemeral CC was that no mutations would be saved there
+    // we don't need to finish the transaction here--the point of the ephemeral CC was that no mutations would be saved
+    // there
     let _ = tx.abort().await;
 
     Ok(HistorySecret { client_id, key_package })

crypto/src/mls/credential/mod.rs

@@ -95,7 +95,8 @@ impl Credential {
     ///
     /// The result is independent of any client instance and the database; it lives in memory only.
     ///
-    /// The earliest validity of this credential is always 0. It will be updated once the credential is added to a session.
+    /// The earliest validity of this credential is always 0. It will be updated once the credential is added to a
+    /// session.
     pub fn basic(ciphersuite: Ciphersuite, client_id: ClientId, crypto: impl OpenMlsCrypto) -> Result<Self> {
         let signature_scheme = ciphersuite.signature_algorithm();
         let (private_key, public_key) = crypto

crypto/src/mls/session/key_package.rs

@@ -55,7 +55,8 @@ impl Session {
     ///
     /// As a side effect, stores the keypackages and some related data in the keystore.
     ///
-    /// Must not be fully public, only crate-public, because as it mutates the keystore it must only ever happen within a transaction.
+    /// Must not be fully public, only crate-public, because as it mutates the keystore it must only ever happen within
+    /// a transaction.
     pub(crate) async fn generate_keypackage(
         &self,
         credential_ref: &CredentialRef,

keystore/src/connection/platform/generic/meta_migrations/v18.rs

@@ -47,7 +47,8 @@ pub(crate) fn meta_migration(conn: &mut rusqlite::Connection) -> CryptoKeystoreR
             secret_key: row.get("secret_key")?,
         };
 
-        // Insert the new credential into temporary mls_credentials_new table, that will be renamed in the next migration
+        // Insert the new credential into temporary mls_credentials_new table, that will be renamed in the next
+        // migration
         if let Some(ciphersuite) = ciphersuite_for_signature_scheme(v6.signature_scheme) {
             tx.execute(
                 "INSERT INTO mls_credentials_new (

keystore/src/migrations.rs

@@ -117,8 +117,8 @@ pub(crate) fn v5_credential_matches_signature_key(
 /// We need to map a signature scheme to a ciphersuite in our migrations. Most of these mappings are unambiguous.
 /// However, we still need to consider the possibility that users are using unexpected signature schemes.
 ///
-/// The strategy here is to perform an analysis of the existing conversations, counting the ciphersuites actually in use.
-/// For each ambiguous signature scheme, there are these possibilities to consider:
+/// The strategy here is to perform an analysis of the existing conversations, counting the ciphersuites actually in
+/// use. For each ambiguous signature scheme, there are these possibilities to consider:
 ///
 /// | Ciphersuite A | Ciphersuite B | Outcome |
 /// |---------------|---------------|---------|