Merge branch 'dev' into 8832-hashvalueerror

Author: e-mny

CONTRIBUTING.md

@@ -303,6 +303,13 @@ By making a contribution to this project, I certify that:
     this project or the open source license(s) involved.
 ```
 
+> **Tip:** If you need to add a DCO remediation commit (e.g., after a force-push
+> or rebase), include `[skip ci]` in the commit message so the remediation
+> does not trigger unnecessary CI pipelines:
+> ```bash
+> git commit -s --allow-empty -m 'DCO Remediation Commit for... [skip ci]'
+> ```
+
 #### Utility functions
 
 MONAI provides a set of generic utility functions and frequently used routines.
@@ -358,6 +365,90 @@ Ideally, the new branch should be based on the latest `dev` branch.
 1. Reviewer and contributor may have discussions back and forth until all comments addressed.
 1. Wait for the pull request to be merged.
 
+## Skipping CI
+
+MONAI's CI pipelines run automatically on every push and pull request.
+These pipelines can be resource-intensive, especially the full premerge matrix
+which spans multiple OSes, Python versions, and PyTorch versions.
+
+To reduce unnecessary resource consumption and speed up iteration, you can
+skip CI on commits that don't need automated validation — for example,
+documentation-only changes, README updates, workflow YAML changes, or WIP
+commits during development.
+
+### Mechanism
+
+GitHub Actions natively supports skipping `push` and `pull_request` workflows
+when the commit message contains any of the following strings:
+
+- `[skip ci]`
+- `[ci skip]`
+- `[no ci]`
+- `[skip actions]`
+- `[actions skip]`
+
+These are case-insensitive. `[skip ci]` is the recommended convention for
+this repository.
+
+Alternatively, you can add a `skip-checks: true` trailer at the end of the
+commit message, preceded by two blank lines:
+
+```
+commit message
+
+skip-checks: true
+```
+
+### Usage
+
+Add the keyword anywhere in the commit message when committing:
+
+```bash
+git commit -s -m 'update docs [skip ci]'
+```
+
+If the HEAD commit of a pull request contains the skip instruction,
+the entire PR's pull_request-triggered workflows are skipped.
+
+### Which workflows are affected
+
+The skip instruction applies only to workflows triggered by `on: push` or
+`on: pull_request` events. All other workflows — those using `issue_comment`,
+`repository_dispatch`, `schedule`, or `workflow_dispatch` — use different
+event types and are **not** affected by `[skip ci]`.
+
+### Important caveat
+
+If a workflow is skipped via `[skip ci]`, its associated checks remain in
+"Pending" state. If your pull request requires those checks to pass before
+merging, you will need to push a new commit **without** the skip instruction
+to trigger the CI pipelines.
+
+### When to use
+
+Use `[skip ci]` for commits that are safe to skip CI:
+
+- Documentation-only changes (`docs/`, `README.md`, docstrings)
+- Workflow configuration changes (`.github/`)
+- Repository metadata (`.gitignore`, `CONTRIBUTING.md`, `LICENSE`)
+- WIP or draft commits during local development
+
+Do **not** use `[skip ci]` for commits that change:
+
+- Source code in `monai/`
+- Test files in `tests/`
+- Dependencies (`requirements*.txt`, `setup.cfg`, `setup.py`)
+- Anything that could affect correctness or compatibility
+
+### Quick example
+
+```bash
+git commit -s -m 'fix typo in README [skip ci]'
+```
+
+This commit will be recorded in the repository history but will not
+consume CI minutes.
+
 ## The code reviewing process
 
 ### Reviewing pull requests

docs/source/lazy_resampling.rst

@@ -253,7 +253,7 @@ so the user must set lazy=True on the transforms that they still wish to execute
 
 .. figure:: ../images/lazy_resampling_none_example.svg
 
-    Figure shwoing the effect of using ``lazy=False`` when ``Compose`` is being executed with ``lazy=None``. Note that
+    Figure showing the effect of using ``lazy=False`` when ``Compose`` is being executed with ``lazy=None``. Note that
     the additional resamples that occur due to ``RandRotate90d`` being executed in a non-lazy fashion.
 
 
@@ -270,4 +270,4 @@ the following transform is a lazy transform, or is configured to execute lazily.
 .. figure:: ../images/lazy_resampling_apply_pending_example.svg
 
     Figure showing the use of :class:`ApplyPendingd<monai.transforms.lazy.dictionary.ApplyPendingd>` to cause
-    resampling to occur in the midele of a chain of lazy transforms.
+    resampling to occur in the middle of a chain of lazy transforms.

docs/source/losses.rst

@@ -78,6 +78,11 @@ Segmentation Losses
 .. autoclass:: BarlowTwinsLoss
     :members:
 
+`BoundaryLoss`
+~~~~~~~~~~~~~~
+.. autoclass:: BoundaryLoss
+    :members:
+
 `HausdorffDTLoss`
 ~~~~~~~~~~~~~~~~~
 .. autoclass:: HausdorffDTLoss

docs/source/modules.md

@@ -205,7 +205,7 @@ The workflow and some of MONAI event handlers are shown as below [[Workflow exam
 
 ### EnsembleEvaluator
 
-A typical ensemble procoess is implemented as a ready-to-use workflow [[Cross validation and model ensemble tutorial]](https://github.com/Project-MONAI/tutorials/blob/main/modules/cross_validation_models_ensemble.ipynb):
+A typical ensemble process is implemented as a ready-to-use workflow [[Cross validation and model ensemble tutorial]](https://github.com/Project-MONAI/tutorials/blob/main/modules/cross_validation_models_ensemble.ipynb):
 1. Split all the training dataset into K folds.
 2. Train K models with every K-1 folds data.
 3. Execute inference on the test data with all the K models.

docs/source/whatsnew_1_5.md

@@ -3,7 +3,7 @@
 
 - Support numpy 2.x and Pytorch 2.6
 - MAISI inference accelerate
-- Bundles storage changed to huggingface and correspoinding api updated in core
+- Bundles storage changed to huggingface and corresponding api updated in core
 - Ported remaining generative tutorials and bundles
 - New tutorials:
   - [2d_regression/image_restoration.ipynb](https://github.com/Project-MONAI/tutorials/blob/main/2d_regression/image_restoration.ipynb)

monai/apps/utils.py

@@ -249,7 +249,7 @@ def download_url(
             if urlparse(url).netloc == "drive.google.com":
                 if not has_gdown:
                     raise RuntimeError("To download files from Google Drive, please install the gdown dependency.")
-                if "fuzzy" not in gdown_kwargs:
+                if "fuzzy" not in gdown_kwargs and not min_version(gdown, "6.0.0"):  # "fuzzy" dropped in gdown 6.0.0
                     gdown_kwargs["fuzzy"] = True  # default to true for flexible url
                 gdown.download(url, f"{tmp_name}", quiet=not progress, **gdown_kwargs)
             elif urlparse(url).netloc == "cloud-api.yandex.net":

monai/bundle/scripts.py

@@ -2005,7 +2005,6 @@ def download_large_files(bundle_path: str | None = None, large_file_name: str |
     parser.read_config(large_file_path)
     large_files_list = parser.get()["large_files"]
     for lf_data in large_files_list:
-        lf_data["fuzzy"] = True
         if "hash_val" in lf_data and lf_data.get("hash_val", "") == "":
             lf_data.pop("hash_val")
         if "hash_type" in lf_data and lf_data.get("hash_type", "") == "":

monai/losses/__init__.py

@@ -14,6 +14,7 @@
 from .adversarial_loss import PatchAdversarialLoss
 from .aucm_loss import AUCMLoss
 from .barlow_twins import BarlowTwinsLoss
+from .boundary_loss import BoundaryLoss
 from .cldice import SoftclDiceLoss, SoftDiceclDiceLoss
 from .contrastive import ContrastiveLoss
 from .deform import BendingEnergyLoss, DiffusionLoss