Merge branch 'master' into fix/nth-element-projections-sentinels

Author: aneek22112007-tech

.cmake-format.py

@@ -585,6 +585,8 @@
     'hpx_extract_includes_from_file': { 'kwargs': { 'SOURCE': 1,
                                                     'INCLUDE_DIRS': '+',
                                                     'FOUND_HEADERS': 1},
+                          'pargs': { 'flags': [], 'nargs': '1+'}},
+    'hpx_configure_module_producer': { 'kwargs': { 'MODULE_OUT_DIR': 1},
                           'pargs': { 'flags': [], 'nargs': '1+'}}
   }
 

.github/CODE_OF_CONDUCT.md

@@ -21,7 +21,7 @@ the spirit in which it's intended - a guide to make it easier to enrich all of
 us and the technical communities in which we participate.
 
 This code of conduct applies to all spaces managed by the
-[HPX](https://github.com/STEllAR-GROUP/hpx) project or
+[HPX](https://github.com/TheHPXProject/hpx) project or
 [STE||AR Group](http://stellar-group.org). This includes IRC, the mailing
 lists, the issue tracker, and any other forums created by the project team
 which the community uses for communication. In addition, violations of this

.github/CONTRIBUTING.md

@@ -4,7 +4,7 @@
 <!-- Distributed under the Boost Software License, Version 1.0. (See accompanying -->
 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)        -->
 
-This describes how you can contribute to [HPX](https://github.com/STEllAR-GROUP/hpx).
+This describes how you can contribute to [HPX](https://github.com/TheHPXProject/hpx).
 Great to have you here. There are a few ways you can help make HPX better!
 
 # How to Get Involved in Developing HPX
@@ -13,7 +13,7 @@ This page describes how you can get yourself involved with the development of
 HPX. Here are some easy things to do.
 
 All of the HPX development and the related discussions happen through the
-[Github ticket system](https://github.com/STEllAR-GROUP/hpx/issues). We are
+[Github ticket system](https://github.com/TheHPXProject/hpx/issues). We are
 looking forward to contributions submitted through the usual Github process,
 i.e. pull requests.
 
@@ -22,7 +22,7 @@ The easiest ways to get in contact with us are listed here:
 * Mailing list:    [hpx-users@stellar-group.org](email:hpx-users@stellar-group.org), [hpx-devel@stellar-group.org](email:hpx-devel@stellar-group.org)
 * Discord server:  [#ste||ar](https://discord.gg/Tn9QuzVjvy)
 * Blog:            [hpx.stellar-group.org](hpx.stellar-group.org)
-* More options:    See our [support page](https://github.com/STEllAR-GROUP/hpx/blob/master/.github/SUPPORT.md)
+* More options:    See our [support page](https://github.com/TheHPXProject/hpx/blob/master/.github/SUPPORT.md)
 
 The basic approach is to find something fun you want to fix, hack it up, and
 send a `git diff` as a mail attachment to [hpx-devel@stellar-group.org](email:hpx-devel@stellar-group.org)
@@ -54,7 +54,7 @@ cleanup that many people can help out with), then please:
 If a task has an owner without an update in a week, feel free to notify them
 that you're taking that on yourself, and of course if you realize you can't
 complete a task - please update it in the
-[ticket system](https://github.com/STEllAR-GROUP/hpx/issues).
+[ticket system](https://github.com/TheHPXProject/hpx/issues).
 
 Even if you are deeply skilled, please consider doing one little easy hack, to
 get used to the process. After that, you are invited to move on up to the more
@@ -72,7 +72,7 @@ information to get you started.
 ### Get a login on Github [here](https://github.com/) and fork the HPX repository to your Github account.
 
 All new and old bugs in HPX can be found in our
-[ticket system](https://github.com/STEllAR-GROUP/hpx/issues). Especially with
+[ticket system](https://github.com/TheHPXProject/hpx/issues). Especially with
 new incoming bugs, it is helpful to test the bug on your own computer/operating
 system and comment in the bug entry whether you can or cannot confirm the bug
 and under what circumstances it affects you.
@@ -104,7 +104,7 @@ The short version of the guidelines:
 * Exceptions for error handling instead of C-style error codes.
 
 A more elaborate description of our coding guidelines can be found
-[here](https://github.com/STEllAR-GROUP/hpx/wiki/HPX-Source-Code-Structure-and-Coding-Standards).
+[here](https://github.com/TheHPXProject/hpx/wiki/HPX-Source-Code-Structure-and-Coding-Standards).
 
 There is a `.editorconfig` file in the HPX root directory which can be used
 for almost any widely available editor. Please see

.github/SECURITY.md

@@ -10,7 +10,7 @@
 
 If you believe you have found a security vulnerability in HPX, don't hesitate to _report them_.
 
- 1. Use any of the [means of contact](https://github.com/STEllAR-GROUP/hpx/blob/master/.github/SUPPORT.md).
+ 1. Use any of the [means of contact](https://github.com/TheHPXProject/hpx/blob/master/.github/SUPPORT.md).
 
     **Please do not report security vulnerabilities through public GitHub issues.**
 

.github/SUPPORT.md

@@ -7,7 +7,7 @@
 ## Support for deploying and using HPX
 
 Welcome to [HPX](http://stellar-group.org/libraries/hpx/)! We use GitHub for
-[tracking bugs and feature requests](https://github.com/STEllAR-GROUP/hpx/issues).
+[tracking bugs and feature requests](https://github.com/TheHPXProject/hpx/issues).
 Please see for the resources below if you are looking for the right place to
 get support for using HPX.
 
@@ -18,7 +18,7 @@ get support for using HPX.
 ### Reporting security issues and vulnerabilities
 
 Please send us an [email](info@stellar-group.org) describing the issue. See our
-[security policy](https://github.com/STEllAR-GROUP/hpx/blob/master/.github/SECURITY.md)
+[security policy](https://github.com/TheHPXProject/hpx/blob/master/.github/SECURITY.md)
 for details.
 
 ### Chat

.github/ci-scripts/generate_ctest_exclude_regex.ps1

@@ -0,0 +1,17 @@
+# Copyright (c) 2026 Arpit Singh
+#
+# SPDX-License-Identifier: BSL-1.0
+# Distributed under the Boost Software License, Version 1.0. (See accompanying
+# file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+
+param(
+    [Parameter(Mandatory = $true)]
+    [string]$Path
+)
+
+$resolved_path = Resolve-Path -Path $Path -ErrorAction Stop
+$exclude_targets = Get-Content -Path $resolved_path |
+    Where-Object { $_ -notmatch '^\s*(#|$)' } |
+    ForEach-Object { $_.Trim() }
+
+[System.String]::Join('|', $exclude_targets)

.github/ci-scripts/generate_test_matrix.py

@@ -66,15 +66,24 @@ def generate_matrix(ctest_output, num_buckets):
             bucket_targets.append(target)
 
         unique_targets = sorted(list(set(bucket_targets)))
-        targets_str = " ".join(unique_targets)
-
-        matrix["include"].append({
-            "id": i + 1,
-            "name": f"tests-{i+1:02d}",
-            "tests": test_regex,
-            "targets": targets_str,
-            "count": len(bucket_tests)
-        })
+        if len(unique_targets) != 0:
+            first_name_parts = unique_targets[0].split('.')
+            last_name_parts = unique_targets[-1].split('.')
+
+            first_name_index = -2 if len(first_name_parts) > 1 else -1
+            last_name_index = -2 if len(last_name_parts) > 1 else -1
+
+            first_name = first_name_parts[first_name_index]
+            last_name = last_name_parts[last_name_index]
+
+            targets_str = " ".join(unique_targets)
+            matrix["include"].append({
+                "id": i + 1,
+                "name": f"{i+1:02d}-{first_name}-{last_name}",
+                "tests": test_regex,
+                "targets": targets_str,
+                "count": len(bucket_tests)
+            })
 
     return matrix
 

.github/workflows/build-and-test.yml

@@ -83,24 +83,24 @@ jobs:
       - name: core_local (Building Core Local)
         shell: bash
         working-directory: build
-        run: ninja -j"$(nproc)" -k 0 hpx_core
+        run: ninja -k 0 hpx_core
 
       - name: core (Building Core)
         shell: bash
         working-directory: build
-        run: ninja -j"$(nproc)" -k 0 core
+        run: ninja -k 0 core
 
       - name: Components (Building Components)
         shell: bash
         working-directory: build
-        run: ninja -j"$(nproc)" -k 0 components
+        run: ninja -k 0 components
 
       - name: Generate Test Matrix
         id: gen_matrix
         shell: bash
         working-directory: build
         run: |
-          ctest -N | python3 ../.github/ci-scripts/generate_test_matrix.py 18 > test_matrix.json
+          ctest -N | python3 ../.github/ci-scripts/generate_test_matrix.py 20 > test_matrix.json
           printf 'matrix=%s\n' "$(cat test_matrix.json)" >> "$GITHUB_OUTPUT"
 
       - name: Package Build Artifacts

.github/workflows/cancel-workflows.yml

@@ -0,0 +1,75 @@
+# Copyright (c) 2026 Arpit Khandelwal
+#
+# SPDX-License-Identifier: BSL-1.0
+# Distributed under the Boost Software License, Version 1.0. (See accompanying
+# file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+
+name: Cancel Workflows
+
+on:
+  pull_request_target:
+    types: [labeled]
+  issue_comment:
+    types: [created]
+
+jobs:
+  cancel-all:
+    # Trigger if label 'cancel-ci' is added OR if a comment contains '/cancel-ci'
+    if: |
+      (github.event_name == 'pull_request_target' && github.event.label.name == 'cancel-ci') ||
+      (github.event_name == 'issue_comment' && github.event.issue.pull_request && contains(github.event.comment.body, '/cancel-ci'))
+    runs-on: ubuntu-latest
+    permissions:
+      actions: write
+      pull-requests: write
+      issues: write
+    steps:
+      - name: Authorize and Extract PR Number
+        id: context
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          AUTHOR_ASSOC: ${{ github.event.comment.author_association }}
+          COMMENT_USER_ID: ${{ github.event.comment.user.id }}
+          PR_AUTHOR_ID: ${{ github.event.issue.user.id }}
+        run: |
+          if [ "$EVENT_NAME" == "issue_comment" ]; then
+            # Authorize: Maintainers (OWNER, MEMBER, COLLABORATOR) or PR Author
+            if [[ "$AUTHOR_ASSOC" =~ ^(OWNER|MEMBER|COLLABORATOR)$ ]] || [ "$COMMENT_USER_ID" == "$PR_AUTHOR_ID" ]; then
+              echo "User authorized."
+            else
+              echo "Error: Unauthorized user attempted to cancel CI."
+              exit 1
+            fi
+            echo "pr_number=${{ github.event.issue.number }}" >> "$GITHUB_OUTPUT"
+          else
+            # Labels addition is already restricted by GitHub to those with write access
+            echo "pr_number=${{ github.event.pull_request.number }}" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Cancel Workflow Runs
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PR_NUMBER: ${{ steps.context.outputs.pr_number }}
+          CURRENT_RUN_ID: ${{ github.run_id }}
+        run: |
+          echo "Cancelling runs for PR #$PR_NUMBER..."
+
+          # Get all runs for the PR that are NOT completed, excluding this current run
+          RUN_IDS=$(gh run list --pr "$PR_NUMBER" --limit 200 --json databaseId,status --jq '.[] | select(.status != "completed" and .databaseId != (env.CURRENT_RUN_ID | tonumber)) | .databaseId')
+
+          if [ -z "$RUN_IDS" ]; then
+            echo "No active runs found to cancel."
+          else
+            echo "Found the following run IDs to cancel:"
+            echo "$RUN_IDS"
+            for ID in $RUN_IDS; do
+              echo "Cancelling run $ID..."
+              gh run cancel "$ID" || echo "Failed to cancel run $ID (it might have already finished)"
+            done
+          fi
+
+          # Remove label if triggered by label
+          if [ "${{ github.event_name }}" == "pull_request_target" ]; then
+            echo "Removing 'cancel-ci' label..."
+            gh pr edit "$PR_NUMBER" --remove-label "cancel-ci" || echo "Failed to remove label"
+          fi

.github/workflows/codeql.yml

@@ -54,7 +54,7 @@ jobs:
         queries: security-and-quality
 
     - name: Install CMake
-      uses: jwlawson/actions-setup-cmake@v2.2
+      uses: lukka/get-cmake@v4.3.2
 
     - name: Install Ninja
       uses: seanmiddleditch/gha-setup-ninja@master