From 2c8cb902c7ae2afce10dcb1400daed932713afbb Mon Sep 17 00:00:00 2001 From: anandhkb Date: Sat, 21 Mar 2026 18:27:14 -0700 Subject: [PATCH 1/3] Add GitHub issue template for numerical instability reports --- .../ISSUE_TEMPLATE/numerical_instability.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/numerical_instability.md diff --git a/.github/ISSUE_TEMPLATE/numerical_instability.md b/.github/ISSUE_TEMPLATE/numerical_instability.md new file mode 100644 index 0000000000..85e818813a --- /dev/null +++ b/.github/ISSUE_TEMPLATE/numerical_instability.md @@ -0,0 +1,25 @@ +--- +name: "Numerical instability" +about: "Report numerical instability (e.g., NaNs/Infs, ill-conditioning, tolerance or scaling issues)" +title: "[NUMERICAL_INSTABILITY]" +labels: "? - Needs Triage, numerical instability" +assignees: '' + +--- + +**Describe the instability** +A clear description of the numerical problem (e.g., NaN/Inf values, unexpected divergence, extreme sensitivity to small input changes). + +**Steps / minimal reproduction** +Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports where possible. Include inputs, API calls, and solver settings (tolerances, scaling, precision) that reproduce the behavior. + +**Expected vs actual behavior** +What you expected numerically, and what you observed (including any error messages or logs). + +**Environment details (please complete the following information):** + - Environment location: [Bare-metal, Docker, Cloud (specify cloud provider)] + - Method of cuOpt install: [conda, Docker, or from source] + - If method of install is [Docker], provide `docker pull` & `docker run` commands used + +**Additional context** +Add any other context (hardware, CUDA/driver versions, data scaling, problem size) that may help diagnose the issue. From 26f76ba39d0c962da3731c30d5a970e860db61e4 Mon Sep 17 00:00:00 2001 From: anandhkb Date: Sat, 21 Mar 2026 18:46:14 -0700 Subject: [PATCH 2/3] Issue templates: link RAPIDS guidelines, clarify cuOpt vs generic RAPIDS --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/numerical_instability.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 452117b53d..211a30923c 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -11,7 +11,7 @@ assignees: '' A clear and concise description of what the bug is. **Steps/Code to reproduce bug** -Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly. +Follow the [RAPIDS issue guidelines](https://docs.rapids.ai/contributing/issues/) (search existing issues first, then describe the problem so it can be understood and reproduced). Use the cuOpt issue template that best fits; the RAPIDS page describes general practices. Provide clear steps (and code or data) so we can reproduce the issue and resolve it more quickly. **Expected behavior** A clear and concise description of what you expected to happen. diff --git a/.github/ISSUE_TEMPLATE/numerical_instability.md b/.github/ISSUE_TEMPLATE/numerical_instability.md index 85e818813a..a1e67a0de4 100644 --- a/.github/ISSUE_TEMPLATE/numerical_instability.md +++ b/.github/ISSUE_TEMPLATE/numerical_instability.md @@ -11,7 +11,7 @@ assignees: '' A clear description of the numerical problem (e.g., NaN/Inf values, unexpected divergence, extreme sensitivity to small input changes). **Steps / minimal reproduction** -Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports where possible. Include inputs, API calls, and solver settings (tolerances, scaling, precision) that reproduce the behavior. +Follow the [RAPIDS issue guidelines](https://docs.rapids.ai/contributing/issues/) (search existing issues first, then describe the problem so it can be understood and reproduced). Use the cuOpt issue template that best fits; the RAPIDS page describes general practices. Include inputs, API calls, and solver settings (tolerances, scaling, precision) that reproduce the behavior. **Expected vs actual behavior** What you expected numerically, and what you observed (including any error messages or logs). From 496a2a99387cf54c7bdef4b078a46711e64b8249 Mon Sep 17 00:00:00 2001 From: Anandh Anandh <102690644+anandhkb@users.noreply.github.com> Date: Mon, 23 Mar 2026 14:44:35 -0700 Subject: [PATCH 3/3] Update numerical_instability.md Rename numerical instability to numerical issue --- .github/ISSUE_TEMPLATE/numerical_instability.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/numerical_instability.md b/.github/ISSUE_TEMPLATE/numerical_instability.md index a1e67a0de4..3a75b0c480 100644 --- a/.github/ISSUE_TEMPLATE/numerical_instability.md +++ b/.github/ISSUE_TEMPLATE/numerical_instability.md @@ -1,13 +1,13 @@ --- -name: "Numerical instability" -about: "Report numerical instability (e.g., NaNs/Infs, ill-conditioning, tolerance or scaling issues)" -title: "[NUMERICAL_INSTABILITY]" -labels: "? - Needs Triage, numerical instability" +name: "Numerical issues" +about: "Report numerical issues (e.g., NaNs/Infs, ill-conditioning, tolerance or scaling issues)" +title: "[NUMERICAL_ISSUES]" +labels: "? - Needs Triage, numerical issues" assignees: '' --- -**Describe the instability** +**Describe the numerical issue** A clear description of the numerical problem (e.g., NaN/Inf values, unexpected divergence, extreme sensitivity to small input changes). **Steps / minimal reproduction**