Skip to content

Commit bc4de6f

Browse files
authored
Merge pull request #982 from anandhkb/release/26.04
Add GitHub issue template for numerical instability reports
2 parents f80d6cf + 4d642d3 commit bc4de6f

2 files changed

Lines changed: 26 additions & 1 deletion

File tree

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ assignees: ''
1111
A clear and concise description of what the bug is.
1212

1313
**Steps/Code to reproduce bug**
14-
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.
14+
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.
1515

1616
**Expected behavior**
1717
A clear and concise description of what you expected to happen.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: "Numerical issues"
3+
about: "Report numerical issues (e.g., NaNs/Infs, ill-conditioning, tolerance or scaling issues)"
4+
title: "[NUMERICAL_ISSUES]"
5+
labels: "? - Needs Triage, numerical issues"
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the numerical issue**
11+
A clear description of the numerical problem (e.g., NaN/Inf values, unexpected divergence, extreme sensitivity to small input changes).
12+
13+
**Steps / minimal reproduction**
14+
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.
15+
16+
**Expected vs actual behavior**
17+
What you expected numerically, and what you observed (including any error messages or logs).
18+
19+
**Environment details (please complete the following information):**
20+
- Environment location: [Bare-metal, Docker, Cloud (specify cloud provider)]
21+
- Method of cuOpt install: [conda, Docker, or from source]
22+
- If method of install is [Docker], provide `docker pull` & `docker run` commands used
23+
24+
**Additional context**
25+
Add any other context (hardware, CUDA/driver versions, data scaling, problem size) that may help diagnose the issue.

0 commit comments

Comments
 (0)