-
Notifications
You must be signed in to change notification settings - Fork 26
Comparing changes
Open a pull request
base repository: IntelPython/dpnp
base: 4b64466
head repository: IntelPython/dpnp
compare: d74afaf
- 13 commits
- 94 files changed
- 4 contributors
Commits on Mar 13, 2026
-
Weekly pre-commit autoupdate (#2808)
This PR updates the `.pre-commit-config.yaml` using `pre-commit autoupdate`.
Configuration menu - View commit details
-
Copy full SHA for 7fae3a6 - Browse repository at this point
Copy the full SHA 7fae3a6View commit details
Commits on Mar 18, 2026
-
Mute expecting runtime warning raised in the test (#2822)
This PR follows up #2792 and marks one more `RuntimeWarning` warning as expected due to possible overflow.
Configuration menu - View commit details
-
Copy full SHA for c5f212a - Browse repository at this point
Copy the full SHA c5f212aView commit details -
Bump styfle/cancel-workflow-action from 0.13.0 to 0.13.1 (#2820)
Bumps [styfle/cancel-workflow-action](https://github.com/styfle/cancel-workflow-action) from 0.13.0 to 0.13.1.
Configuration menu - View commit details
-
Copy full SHA for 7d9765b - Browse repository at this point
Copy the full SHA 7d9765bView commit details -
Weekly pre-commit autoupdate (#2818)
This PR updates the `.pre-commit-config.yaml` using `pre-commit autoupdate`.
Configuration menu - View commit details
-
Copy full SHA for 19efa58 - Browse repository at this point
Copy the full SHA 19efa58View commit details -
Bump actions/download-artifact from 8.0.0 to 8.0.1 (#2819)
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 8.0.0 to 8.0.1.
Configuration menu - View commit details
-
Copy full SHA for 3a6af45 - Browse repository at this point
Copy the full SHA 3a6af45View commit details -
Bump github/codeql-action from 4.32.4 to 4.32.6 (#2809)
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 4.32.4 to 4.32.6.
Configuration menu - View commit details
-
Copy full SHA for 506a775 - Browse repository at this point
Copy the full SHA 506a775View commit details -
Bump mshick/add-pr-comment from 2.8.2 to 3.9.0 (#2821)
Bumps [mshick/add-pr-comment](https://github.com/mshick/add-pr-comment) from 2.8.2 to 3.9.0.
Configuration menu - View commit details
-
Copy full SHA for cba3d51 - Browse repository at this point
Copy the full SHA cba3d51View commit details -
Upgrade
clang-formatto v22 and improvepylintpre-commit configu……ration (#2813) ## Summary - Migrate clang-format from `pocc/pre-commit-hooks` to `pre-commit/mirrors-clang-format` v22.1.0 - Update `.clang-format` config to maintain consistent code style across versions - Configure pylint to properly handle C extension modules (numpy, dpctl) - Remove manual clang-format-12 installation from GitHub workflow - Reformat all C++ files with clang-format v22 - Add reformatting commit to `.git-blame-ignore-revs` ## Changes ### Pre-commit configuration - Switch to `pre-commit/mirrors-clang-format` (v22.1.0) for better version pinning and consistency across environments - Add `--disable=c-extension-no-member` to pylint to avoid false positives on C extension objects ### Code style - Update `.clang-format`: Set `AfterControlStatement: Never` to preserve existing brace placement style - Reformat all C++ source files with clang-format v22 (net -159 lines due to template parameter formatting improvements) ### Pylint configuration - Add `extension-pkg-allow-list = ["numpy"]` to help pylint understand numpy better - Add `generated-members` patterns to handle dynamically created attributes on numpy types ### CI/CD - Remove obsolete `apt-get install clang-format-12` step from pre-commit workflow
Configuration menu - View commit details
-
Copy full SHA for 21d5e1a - Browse repository at this point
Copy the full SHA 21d5e1aView commit details -
Resolve an issue with
.data.ptrignoring USM offset on array views (#……2812) The `create_data()` function had an early return when `usm_data` was already a dpnp memory class instance, which skipped setting the `ptr` attribute. This caused all array views to report the same base pointer, making `arr[0].data.ptr == arr[1].data.ptr` even though they point to different memory locations. The PR proposes a fix ensuring `ptr` is always set to `x._pointer`, which points to the start of the array's data (including any offset for views), rather than `usm_data._pointer` which points to the base buffer. Additionally, always create a new memory wrapper instance to avoid shared state when the same `usm_data` is used for multiple views. This PR closes #2781. - [x] Have you provided a meaningful PR description? - [x] Have you added a test, reproducer or referred to an issue with a reproducer? - [x] Have you tested your changes locally for CPU and GPU devices? - [x] Have you made sure that new changes do not introduce compiler warnings? - [ ] Have you checked performance impact of proposed changes? - [ ] Have you added documentation for your changes, if necessary? - [x] Have you added your changes to the changelog?
Configuration menu - View commit details
-
Copy full SHA for 54d2109 - Browse repository at this point
Copy the full SHA 54d2109View commit details
Commits on Mar 19, 2026
-
Fix
diagonal()strides calculation for empty results (#2814)Previously `dpnp.diagonal()` returned incorrect strides when the diagonal was empty (e.g., when offset >= array width). The stride was set to itemsize instead of the correct `st_n + st_m`. This PR: * fixes stride calculation to consistently use (st_n + st_m) * simplifies implementation using unified formula to calculate resulting shape, strides, and offset * extends tests coverage including scenarios with empty diagonals, views, and non-contiguous arrays The PR closes #2761.
Configuration menu - View commit details
-
Copy full SHA for db486b9 - Browse repository at this point
Copy the full SHA db486b9View commit details -
Update QR tests to avoid element-wise comparisons (#2785)
This PR proposes updating QR tests to avoid direct element-wise comparisons which became unstable with oneMKL 2026.0 due to sign and phase differences in otherwise valid QR results Since QR factorization is not unique, different MKL and NumPy versions may return results that differ by sign or complex phase while still representing a correct decomposition To make the tests more stable this PR proposes using invariant-based validation for `mode="raw"` and `mode="r"` based on the unitarity of the Q factor (Q^H Q = I) and the resulting QR identity R^H @ R = A^H @ A
Configuration menu - View commit details
-
Copy full SHA for 95ab6a0 - Browse repository at this point
Copy the full SHA 95ab6a0View commit details -
Consolidate SYCL kernels under a single folder (#2816)
This PR moves all SYCL kernel functors from extensions/ to kernels/ directory, improving the project structure. Moved kernels: - statistics: histogram, sliding_window1d functors - indexing: choose functor - window: bartlett, blackman, hamming, hanning, kaiser functors The PR also improves the code coverage report, since the SYCL kernels can be easy excluded from the report now.
Configuration menu - View commit details
-
Copy full SHA for c8c0f88 - Browse repository at this point
Copy the full SHA c8c0f88View commit details
Commits on Mar 20, 2026
-
Add ndarray subclassing support via
ndarray.view()method (#2815)The PR adds ndarray subclassing support via `ndarray.view()` method. It implements the `type` parameter in `dpnp.ndarray.view()` to enable custom subclasses, matching NumPy/CuPy behavior. Also includes proper `__array_finalize__` hook invocation for metadata propagation. The implementation is done through `_view_impl()` helper using 'array_class' parameter to avoid shadowing builtin 'type'. The tests scope is extended with new 7 tests for verifying subclassing support and enabling `TestSubclassArrayView` class from third party tests. This PR closes #2764.
Configuration menu - View commit details
-
Copy full SHA for d74afaf - Browse repository at this point
Copy the full SHA d74afafView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 4b64466...d74afaf