Correct a bug that would overwrite the output_coord_ranges dictionary if feature order in datastore.yaml is incorrect.

.flake8

@@ -1,6 +1,6 @@
-[flake8]
-max-line-length = 88
-extend-ignore = E203, E713, W604, E231
-select = C,E,F,W,B,B950
-ignore = E203, E501, W503
-per-file-ignores = __init__.py:F401
+[flake8]
+max-line-length = 88
+extend-ignore = E203, E713, W604, E231
+select = C,E,F,W,B,B950
+ignore = E203, E501, W503
+per-file-ignores = __init__.py:F401

.github/pull_request_template.md

@@ -1,52 +1,52 @@
-## Describe your changes
-
-< Summary of the changes.>
-
-< Please also include relevant motivation and context. >
-
-< List any dependencies that are required for this change. >
-
-## Issue Link
-
-< Link to the relevant issue or task. > (e.g. `closes #00` or `solves #00`)
-
-## Type of change
-
-- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
-- [ ] ✨ New feature (non-breaking change that adds functionality)
-- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 📖 Documentation (Addition or improvements to documentation)
-
-## Checklist before requesting a review
-
-- [ ] My branch is up-to-date with the target branch - if not update your fork with the changes from the target branch (use `pull` with `--rebase` option if possible).
-- [ ] I have performed a self-review of my code
-- [ ] For any new/modified functions/classes I have added docstrings that clearly describe its purpose, expected inputs and returned values
-- [ ] I have placed in-line comments to clarify the intent of any hard-to-understand passages of my code
-- [ ] I have updated the documentation to cover introduced code changes
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] I have given the PR a name that clearly describes the change, written in imperative form ([context](https://www.gitkraken.com/learn/git/best-practices/git-commit-message#using-imperative-verb-form)).
-- [ ] I have requested a reviewer and an assignee (assignee is responsible for merging)
-
-## Checklist for reviewers
-
-Each PR comes with its own improvements and flaws. The reviewer should check the following:
-- [ ] the code is readable
-- [ ] the code is well tested
-- [ ] the code is documented (including return types and parameters)
-- [ ] the code is easy to maintain
-
-## Author checklist after completed review
-
-- [ ] I have added a line to the CHANGELOG describing this change, in a section
-  reflecting type of change (add section where missing):
-  - *added*: when you have added new functionality
-  - *changed*: when default behaviour of the code has been changed
-  - *fixes*: when your contribution fixes a bug
-
-## Checklist for assignee
-
-- [ ] PR is up to date with the base branch
-- [ ] the tests pass
-- [ ] author has added an entry to the changelog (and designated the change as *added*, *changed* or *fixed*)
-- Once the PR is ready to be merged, squash commits and merge the PR.
+## Describe your changes
+
+< Summary of the changes.>
+
+< Please also include relevant motivation and context. >
+
+< List any dependencies that are required for this change. >
+
+## Issue Link
+
+< Link to the relevant issue or task. > (e.g. `closes #00` or `solves #00`)
+
+## Type of change
+
+- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
+- [ ] ✨ New feature (non-breaking change that adds functionality)
+- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] 📖 Documentation (Addition or improvements to documentation)
+
+## Checklist before requesting a review
+
+- [ ] My branch is up-to-date with the target branch - if not update your fork with the changes from the target branch (use `pull` with `--rebase` option if possible).
+- [ ] I have performed a self-review of my code
+- [ ] For any new/modified functions/classes I have added docstrings that clearly describe its purpose, expected inputs and returned values
+- [ ] I have placed in-line comments to clarify the intent of any hard-to-understand passages of my code
+- [ ] I have updated the documentation to cover introduced code changes
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have given the PR a name that clearly describes the change, written in imperative form ([context](https://www.gitkraken.com/learn/git/best-practices/git-commit-message#using-imperative-verb-form)).
+- [ ] I have requested a reviewer and an assignee (assignee is responsible for merging)
+
+## Checklist for reviewers
+
+Each PR comes with its own improvements and flaws. The reviewer should check the following:
+- [ ] the code is readable
+- [ ] the code is well tested
+- [ ] the code is documented (including return types and parameters)
+- [ ] the code is easy to maintain
+
+## Author checklist after completed review
+
+- [ ] I have added a line to the CHANGELOG describing this change, in a section
+  reflecting type of change (add section where missing):
+  - *added*: when you have added new functionality
+  - *changed*: when default behaviour of the code has been changed
+  - *fixes*: when your contribution fixes a bug
+
+## Checklist for assignee
+
+- [ ] PR is up to date with the base branch
+- [ ] the tests pass
+- [ ] author has added an entry to the changelog (and designated the change as *added*, *changed* or *fixed*)
+- Once the PR is ready to be merged, squash commits and merge the PR.

.github/workflows/ci-pre-commit.yml

@@ -1,21 +1,21 @@
-name: linting
-
-on:
-  push:
-    branches: "*"
-  pull_request:
-    branches: "*"
-
-jobs:
-  linting:
-    name: "pre-commit hooks"
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
-        with:
-          # don't use python3.12 because flake8 finds extra issues with that
-          # version
-          python-version: "3.11"
-      - uses: pre-commit/[email protected]
+name: linting
+
+on:
+  push:
+    branches: "*"
+  pull_request:
+    branches: "*"
+
+jobs:
+  linting:
+    name: "pre-commit hooks"
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+        with:
+          # don't use python3.12 because flake8 finds extra issues with that
+          # version
+          python-version: "3.11"
+      - uses: pre-commit/[email protected]

.github/workflows/ci-pypi-deploy.yml

@@ -1,24 +1,24 @@
-name: package-release
-
-on:
-  workflow_dispatch:
-  pull_request:
-  push:
-    branches:
-     - main
-  release:
-    types:
-      - published
-
-jobs:
-  build:
-    name: build and upload release to pypi
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
-      - uses: casperdcl/deploy-pypi@v2
-        with:
-          password: ${{ secrets.PYPI_TOKEN }}
-          pip: wheel -w dist/ --no-deps .
-          upload: ${{ github.event_name == 'release' && github.event.action == 'published' }}
+name: package-release
+
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+     - main
+  release:
+    types:
+      - published
+
+jobs:
+  build:
+    name: build and upload release to pypi
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+      - uses: casperdcl/deploy-pypi@v2
+        with:
+          password: ${{ secrets.PYPI_TOKEN }}
+          pip: wheel -w dist/ --no-deps .
+          upload: ${{ github.event_name == 'release' && github.event.action == 'published' }}

.github/workflows/python-package-pip.yml

@@ -1,49 +1,49 @@
-name: pytest
-
-on:
- push:
-    branches:
-    - main
- pull_request:
-    branches:
-    - main
-
-jobs:
-  test:
-    name: Test pip install python ${{ matrix.python-version }} on ${{ matrix.os }} with zarr ${{ matrix.zarr-version }}
-
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        os: [ubuntu-latest]
-        python-version: ["3.9", "3.10"]
-        zarr-version: [">=2,<3", ">2,<=3"]
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v2
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Install package with pip
-        run: |
-          python -m pip install . "zarr${{ matrix.zarr-version }}"
-          python -m pip install pytest
-
-      - name: Run tests (non-distributed)
-        env:
-          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-        run: |
-          python -m pytest tests/
-      - name: Install distributed dependencies
-        run: |
-          python -m pip install .[dask-distributed]
-      - name: Run tests (distributed)
-        env:
-          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-        run: |
-          python -m pytest tests/
+name: pytest
+
+on:
+ push:
+    branches:
+    - main
+ pull_request:
+    branches:
+    - main
+
+jobs:
+  test:
+    name: Test pip install python ${{ matrix.python-version }} on ${{ matrix.os }} with zarr ${{ matrix.zarr-version }}
+
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest]
+        python-version: ["3.9", "3.10"]
+        zarr-version: [">=2,<3", ">2,<=3"]
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package with pip
+        run: |
+          python -m pip install . "zarr${{ matrix.zarr-version }}"
+          python -m pip install pytest
+
+      - name: Run tests (non-distributed)
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+        run: |
+          python -m pytest tests/
+      - name: Install distributed dependencies
+        run: |
+          python -m pip install .[dask-distributed]
+      - name: Run tests (distributed)
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+        run: |
+          python -m pytest tests/