Merge remote-tracking branch 'origin/main' into async-dtreec

Author: aladinor

.github/nightly-wheel-failure-template.md

@@ -0,0 +1,11 @@
+# Nightly Wheel Build/Upload Failed
+
+**Workflow:** {{WORKFLOW}}
+**Run:** [{{RUN_ID}}]({{RUN_URL}})
+**Date:** {{DATE}}
+
+The nightly wheel build or upload to the `scientific-python-nightly-wheels` index has failed.
+
+Please check the [workflow run]({{RUN_URL}}) for details.
+
+This issue was automatically generated from the nightly wheel workflow.

.github/workflows/nightly-wheels.yml

@@ -3,6 +3,11 @@ on:
   workflow_dispatch:
   schedule:
     - cron: "0 0 * * *"
+
+permissions:
+  contents: read
+  issues: write
+
 jobs:
   cron:
     runs-on: ubuntu-latest
@@ -21,12 +26,14 @@ jobs:
           python -m pip install build twine
 
       - name: Build tarball and wheels
+        id: build
         run: |
           git clean -xdf
           git restore -SW .
           python -m build
 
       - name: Check built artifacts
+        id: check
         run: |
           python -m twine check --strict dist/*
           pwd
@@ -38,7 +45,40 @@ jobs:
           fi
 
       - name: Upload wheel
+        id: upload
         uses: scientific-python/upload-nightly-action@5748273c71e2d8d3a61f3a11a16421c8954f9ecf # 0.6.3
         with:
           anaconda_nightly_upload_token: ${{ secrets.ANACONDA_NIGHTLY }}
           artifacts_path: dist
+
+      - name: Create or update failure issue
+        if: ${{ failure() }}
+        shell: bash
+        run: |
+          # Read the template
+          template=$(cat .github/nightly-wheel-failure-template.md)
+
+          # Replace placeholders
+          issue_body="${template//\{\{WORKFLOW\}\}/${{ github.workflow }}}"
+          issue_body="${issue_body//\{\{RUN_ID\}\}/${{ github.run_id }}}"
+          issue_body="${issue_body//\{\{RUN_URL\}\}/${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}}"
+          issue_body="${issue_body//\{\{DATE\}\}/$(date -u)}"
+
+          # Check for existing open issue with same title
+          issue_title="Nightly wheel build/upload failed"
+          existing_issue=$(gh issue list --state open --label "CI" --search "\"$issue_title\" in:title" --json number --jq '.[0].number // empty')
+
+          if [ -n "$existing_issue" ]; then
+            echo "Found existing open issue #$existing_issue, updating it..."
+            echo "$issue_body" | gh issue edit "$existing_issue" --body-file -
+            echo "Updated existing issue #$existing_issue"
+          else
+            echo "No existing open issue found, creating new one..."
+            echo "$issue_body" | gh issue create \
+              --title "$issue_title" \
+              --body-file - \
+              --label "CI"
+            echo "Created new issue"
+          fi
+        env:
+          GH_TOKEN: ${{ github.token }}

doc/contribute/contributing.rst

@@ -576,7 +576,7 @@ a user passes ``old_arg``, we would instead catch it:
             emit_user_level_warning(
                 "`old_arg` has been deprecated, and in the future will raise an error."
                 "Please use `new_arg` from now on.",
-                DeprecationWarning,
+                FutureWarning,
             )
 
             # Still do what the user intended here

doc/get-help/faq.rst

@@ -423,7 +423,7 @@ How stable is Xarray's API?
 
 Xarray tries very hard to maintain backwards compatibility in our :ref:`api` between released versions.
 Whilst we do occasionally make breaking changes in order to improve the library,
-we `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``DeprecationWarnings`` for many releases in advance.
+we `signpost changes <https://docs.xarray.dev/en/stable/contributing.html#backwards-compatibility>`_ with ``FutureWarnings`` for many releases in advance.
 (An exception is bugs - whose behaviour we try to fix as soon as we notice them.)
 Our `test-driven development practices <https://docs.xarray.dev/en/stable/contributing.html#test-driven-development-code-writing>`_ helps to ensure any accidental regressions are caught.
 This philosophy applies to everything in the `public API <https://docs.xarray.dev/en/stable/getting-started-guide/faq.html#what-parts-of-xarray-are-considered-public-api>`_.

doc/user-guide/io.rst

@@ -311,7 +311,7 @@ __ https://www.unidata.ucar.edu/software/netcdf/
     If you aren't familiar with this data format, the `netCDF FAQ`_ is a good
     place to start.
 
-.. _netCDF FAQ: https://www.unidata.ucar.edu/software/netcdf/docs/faq.html#What-Is-netCDF
+.. _netCDF FAQ: https://docs.unidata.ucar.edu/netcdf-c/current/faq.html
 
 Reading and writing netCDF files with xarray requires scipy, h5netcdf, or the
 `netCDF4-Python`__ library to be installed. SciPy only supports reading and writing

doc/whats-new.rst

@@ -18,10 +18,20 @@ New Features
   the maximum number of concurrent I/O operations when opening groups in parallel
   with the Zarr backend (:pull:`10742`).
   By `Alfonso Ladino <https://github.com/aladinor>`_.
+- :py:class:`~xarray.indexes.NDPointIndex` now supports coordinates with fewer
+  dimensions than coordinate variables, enabling indexing of scattered points
+  and trajectories where multiple coordinates (e.g., ``x``, ``y``) share a
+  single dimension (e.g., ``points``) (:issue:`10940`, :pull:`11116`).
+  By `Ian Hunt-Isaak <https://github.com/ianhi>`_.
 
 Breaking Changes
 ~~~~~~~~~~~~~~~~
 
+- When deprecating functionality, xarray has sometimes used ``FutureWarning``
+  and sometimes used ``DeprecationWarning``. ``DeprecationWarning`` is
+  not intended to be visible to end-users so this version of xarray
+  switches to using ``FutureWarning`` everywhere (:pull:`11112`).
+  By `Julia Signell <https://github.com/jsignell>`_.
 
 Deprecations
 ~~~~~~~~~~~~
@@ -30,6 +40,8 @@ Deprecations
 Bug Fixes
 ~~~~~~~~~
 
+- Fix slicing with negative step (:issue:`11000` and :pull:`11044`).
+  By `Antonio Valentino <https://github.com/avalentino>`_.
 - Fix ``.plot`` error when using positional args with ``col`` and
   ``row`` (:issue:`11104` :pull:`11111`).
   By `Julia Signell <https://github.com/jsignell>`_.
@@ -38,6 +50,9 @@ Bug Fixes
 - Fix silent data corruption when writing dask arrays to sharded Zarr stores.
   Dask chunk boundaries must now align with shard boundaries, not just internal
   Zarr chunk boundaries (:issue:`10831`).
+- Fix :py:meth:`Dataset.sortby` and :py:meth:`DataArray.sortby` placing NaN values
+  at the beginning instead of the end when using ``ascending=False`` (:issue:`7358`).
+  By `Kristian Kollsgård <https://github.com/kkollsga>`_.
 
 Documentation
 ~~~~~~~~~~~~~

pixi.toml

@@ -5,7 +5,7 @@ platforms = ["win-64", "linux-64", "osx-arm64"]
 
 [package]
 name = "xarray"
-version = "dynamic" # dynamic versioning needs better support in pixi https://github.com/prefix-dev/pixi/issues/2923#issuecomment-2598460666 . Putting `version = "dynamic"` here for now until pixi recommends something else.
+version = "9999.0.0" # dynamic versioning needs better support in pixi https://github.com/prefix-dev/pixi/issues/2923#issuecomment-2598460666 . Putting `version = "..."` here for now until pixi recommends something else.
 
 [package.build]
 backend = { name = "pixi-build-python", version = ">=0.4.4" }
@@ -238,9 +238,7 @@ sphinxcontrib-srclinks = "*"
 sphinx-remove-toctrees = "*"
 sphinxext-opengraph = "*"
 sphinxext-rediraffe = "*"
-
-[feature.doc.pypi-dependencies]
-cfgrib = "*" # pypi dep because of https://github.com/prefix-dev/pixi/issues/3032#issuecomment-3302638043
+cfgrib = "*"
 
 [feature.doc.tasks]
 doc = { cmd = "make html", cwd = "doc" }

properties/test_index_manipulation.py

@@ -195,9 +195,9 @@ def drop_dims(self, data):
             )
         )
         note(f"> drop_dims: {dims}")
-        # TODO: dropping a multi-index dimension raises a DeprecationWarning
+        # TODO: dropping a multi-index dimension raises a FutureWarning
         with warnings.catch_warnings():
-            warnings.simplefilter("ignore", category=DeprecationWarning)
+            warnings.simplefilter("ignore", category=FutureWarning)
             self.dataset = self.dataset.drop_dims(dims)
 
         for dim in dims:

xarray/backends/pydap_.py

@@ -123,7 +123,7 @@ def open(
             emit_user_level_warning(
                 "`output_grid` is deprecated and will be removed in a future version"
                 " of xarray. Will be set to `None`, the new default. ",
-                DeprecationWarning,
+                FutureWarning,
             )
             output_grid = False  # new default behavior
 

xarray/backends/writers.py

@@ -567,7 +567,7 @@ def save_mfdataset(
     <xarray.Dataset> Size: 768B
     Dimensions:  (time: 48)
     Coordinates:
-      * time     (time) datetime64[ns] 384B 2010-01-31 2010-02-28 ... 2013-12-31
+      * time     (time) datetime64[us] 384B 2010-01-31 2010-02-28 ... 2013-12-31
     Data variables:
         a        (time) float64 384B 0.0 0.02128 0.04255 ... 0.9574 0.9787 1.0
     >>> years, datasets = zip(*ds.groupby("time.year"))