Fix typos: accidentally (ruff.toml), partial (solver_api.py)

Made-with: Cursor

Author: bknox83

chia/solver/solver_api.py

@@ -36,7 +36,7 @@ async def solve(
     ) -> Message | None:
         """
         Solve a V2 plot partial proof to get the full proof of space.
-        This is called by the farmer when it receives V2 parital proofs from harvester.
+        This is called by the farmer when it receives V2 partial proofs from harvester.
         """
         if not self.solver.started:
             self.log.error("Solver is not started")
@@ -47,7 +47,7 @@ async def solve(
         try:
             proof = self.solver.solve(request.partial_proof, request.plot_id, request.strength, request.size)
             if proof is None:
-                self.log.warning(f"Solver returned no proof for parital {request.partial_proof.fragments[:5]}")
+                self.log.warning(f"Solver returned no proof for partial {request.partial_proof.fragments[:5]}")
                 return None
 
             self.log.debug(f"Successfully solved partial proof, returning {len(proof)} byte proof")
@@ -57,5 +57,5 @@ async def solve(
             )
 
         except Exception as e:
-            self.log.error(f"Error solving parital {request.partial_proof.fragments[:5]}: {e}")
+            self.log.error(f"Error solving partial {request.partial_proof.fragments[:5]}: {e}")
             return None

ruff.toml

@@ -46,7 +46,7 @@ ignore = [
     # Ruff Specific
 
     # This code is problematic because using instantiated types as defaults is so common across the codebase.
-    # Its purpose is to prevent accidenatally assigning mutable defaults. However, this is a bit overkill for that.
+    # Its purpose is to prevent accidentally assigning mutable defaults. However, this is a bit overkill for that.
     # That being said, it would be nice to add some way to actually guard against that specific mutable default behavior.
     "RUF009", # function-call-in-dataclass-default-argument
     "RUF056", # falsy-dict-get-fallback