From 0ad39eb69a4f37749970a34a34e7df2c4f3c9220 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Tue, 15 Oct 2024 15:22:44 -0400 Subject: [PATCH] [DATALAD RUNCMD] Do interactive fixing of some ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w -i 3 -C 2", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ --- README.md | 2 +- docs/docs/icechunk-python/virtual.md | 2 +- docs/docs/overview.md | 2 +- icechunk-python/src/errors.rs | 2 +- icechunk/src/refs.rs | 2 +- icechunk/src/zarr.rs | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index fecf64b81..80d88ffe0 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ Arrays have two fundamental properties: In Zarr / Icechunk, arrays are split into **chunks**, A chunk is the minimum unit of data that must be read / written from storage, and thus choices about chunking have strong implications for performance. Zarr leaves this completely up to the user. -Chunk shape should be chosen based on the anticipated data access patten for each array +Chunk shape should be chosen based on the anticipated data access pattern for each array An Icechunk array is not bounded by an individual file and is effectively unlimited in size. For further organization of data, Icechunk supports **groups** within a single repo. diff --git a/docs/docs/icechunk-python/virtual.md b/docs/docs/icechunk-python/virtual.md index 0fdc0f48f..b86e70dde 100644 --- a/docs/docs/icechunk-python/virtual.md +++ b/docs/docs/icechunk-python/virtual.md @@ -4,7 +4,7 @@ While Icechunk works wonderfully with native chunks managed by Zarr, there is lo !!! warning - While virtual references are fully supported in Icechunk, creating virtual datasets currently relies on using experimental or pre-release versions of open source tools. For full instructions on how to install the required tools and ther current statuses [see the tracking issue on Github](https://github.com/earth-mover/icechunk/issues/197). + While virtual references are fully supported in Icechunk, creating virtual datasets currently relies on using experimental or pre-release versions of open source tools. For full instructions on how to install the required tools and their current statuses [see the tracking issue on Github](https://github.com/earth-mover/icechunk/issues/197). With time, these experimental features will make their way into the released packages. To create virtual Icechunk datasets with Python, the community utilizes the [kerchunk](https://fsspec.github.io/kerchunk/) and [VirtualiZarr](https://virtualizarr.readthedocs.io/en/latest/) packages. diff --git a/docs/docs/overview.md b/docs/docs/overview.md index 55a685536..e19ad7cea 100644 --- a/docs/docs/overview.md +++ b/docs/docs/overview.md @@ -63,7 +63,7 @@ Arrays have two fundamental properties: In Zarr / Icechunk, arrays are split into **chunks**, A chunk is the minimum unit of data that must be read / written from storage, and thus choices about chunking have strong implications for performance. Zarr leaves this completely up to the user. -Chunk shape should be chosen based on the anticipated data access patten for each array +Chunk shape should be chosen based on the anticipated data access pattern for each array An Icechunk array is not bounded by an individual file and is effectively unlimited in size. For further organization of data, Icechunk supports **groups** within a single repo. diff --git a/icechunk-python/src/errors.rs b/icechunk-python/src/errors.rs index 2323012c3..8fd133dd7 100644 --- a/icechunk-python/src/errors.rs +++ b/icechunk-python/src/errors.rs @@ -10,7 +10,7 @@ use thiserror::Error; /// A simple wrapper around the StoreError to make it easier to convert to a PyErr /// /// When you use the ? operator, the error is coerced. But if you return the value it is not. -/// So for now we just use the extra operation to get the coersion instead of manually mapping +/// So for now we just use the extra operation to get the coercion instead of manually mapping /// the errors where this is returned from a python class #[allow(clippy::enum_variant_names)] #[derive(Debug, Error)] diff --git a/icechunk/src/refs.rs b/icechunk/src/refs.rs index e2399b816..bb52912af 100644 --- a/icechunk/src/refs.rs +++ b/icechunk/src/refs.rs @@ -310,7 +310,7 @@ mod tests { /// Execute the passed block with all test implementations of Storage. /// - /// Currently this function executes agains the in-memory and local filesystem object_store + /// Currently this function executes against the in-memory and local filesystem object_store /// implementations. async fn with_test_storages< R, diff --git a/icechunk/src/zarr.rs b/icechunk/src/zarr.rs index 5b639bca6..ea94ca61a 100644 --- a/icechunk/src/zarr.rs +++ b/icechunk/src/zarr.rs @@ -754,7 +754,7 @@ impl Store { .list_prefix(prefix) .await? .map_ok(move |s| { - // If the prefix is "/", get rid of it. This can happend when prefix is missing + // If the prefix is "/", get rid of it. This can happen when prefix is missing // the trailing slash (as it does in zarr-python impl) let rem = &s[idx..].trim_start_matches('/'); let parent = rem.split_once('/').map_or(*rem, |(parent, _)| parent);