Skip to content

Add GitHub issue template for numerical instability reports #982

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
anandhkb merged 4 commits into from
Mar 30, 2026
Merged

Add GitHub issue template for numerical instability reports #982

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2c8cb90
Add GitHub issue template for numerical instability reports
anandhkb Mar 22, 2026
26f76ba
Issue templates: link RAPIDS guidelines, clarify cuOpt vs generic RAPIDS
anandhkb Mar 22, 2026
496a2a9
Update numerical_instability.md
anandhkb Mar 23, 2026
4d642d3
Merge branch 'release/26.04' into release/26.04
anandhkb Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/numerical_instability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
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 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**
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).

**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.