|
1 | 1 | --- |
2 | | -name: 🐛 Bug Report |
3 | | -about: If something isn't working as expected 🤔. |
4 | | - |
| 2 | +name: Bug Report |
| 3 | +about: If something isn't working as expected. |
5 | 4 | --- |
6 | 5 |
|
7 | 6 | ## Bug Report |
8 | 7 |
|
9 | 8 | ### Steps to Reproduce: |
10 | | - 1. ...step 1 description... |
11 | | - 2. ...step 2 description... |
12 | | - 3. ...step 3 description... |
| 9 | + |
| 10 | +Please provide a full reproduction of the issue. There are three ways we accept |
| 11 | +repros: |
| 12 | + |
| 13 | +1. If the issue you are reporting is a UX/UI issue which can be recreated by |
| 14 | + visiting a Perspective demo _hosted by the project itself_, and any dataset |
| 15 | + required to reproduce the error can be included in the report. In this case, |
| 16 | + please provide detailed step-by-step instructions on how to reproduce, |
| 17 | + including any screenshots which help illustrate, as well as including any |
| 18 | + fully-encoded test data we may need. |
| 19 | + |
| 20 | +2. If you are reporting a build or installation issue with the library itself, |
| 21 | + which can be recreated from a shell. In this case, please provided detailed |
| 22 | + code blocks describing how you tried to install, which commands were issued, |
| 23 | + including and dependencies you needed to install and hwo you installed them. |
| 24 | + |
| 25 | +3. If you are reporting a _anything else_, including but not limited to: |
| 26 | + |
| 27 | + - Build issues which require _any_ metadata files e.g. a `package.json`, |
| 28 | + `Cargo.toml`, etc |
| 29 | + - Bundler or packaging errors with JavaScript |
| 30 | + - Library functions which return the wrong results or error |
| 31 | + - CPU or memory usage performance regressions, or regressions in thread |
| 32 | + utilization |
| 33 | + |
| 34 | + In this case, we require a _complete reproduction_ of the issue in the form |
| 35 | + of a repository. Quoting this exceptional definition from |
| 36 | + [@Rich-Harris's micro-essay on Repros](https://gist.github.com/Rich-Harris/88c5fc2ac6dc941b22e7996af05d70ff), |
| 37 | + please follow these guidelines: |
| 38 | + |
| 39 | + > 1. Create a sample repo on GitHub (or wherever) |
| 40 | + > 2. Demonstrate the problem, and nothing but the problem. If the app where |
| 41 | + > you're experiencing the issue happens to use Gulp, I don't care, |
| 42 | + > unless the problem involves Gulp. Remove that stuff. Whittle it down |
| 43 | + > to the _bare minimum_ of code that reliably demonstrates the issue. |
| 44 | + > Get rid of any dependencies that aren't _directly_ related to the |
| 45 | + > problem. |
| 46 | + > 3. Install all your dependencies to `package.json`. If I can't clone the |
| 47 | + > repo and do `npm install && npm run build` (or similar – see point 4) |
| 48 | + > to see the problem, because I need some globally installed CLI tool or |
| 49 | + > whatever, then you've made it harder to get to the bottom of the |
| 50 | + > issue. |
| 51 | + > 4. Include instructions in the repo, along with a description of the |
| 52 | + > expected and actual behaviour. Obviously the issue should include |
| 53 | + > information about the bug as well, but it's really helpful if |
| 54 | + > `README.md` includes that information, plus a link back to the issue. |
| 55 | + > If there are any instructions beyond `npm install && npm run build`, |
| 56 | + > they should go here. |
| 57 | +
|
| 58 | + Some examples which _do not_ qualify as _complete_ and are mostly useless to |
| 59 | + us for debugging: |
| 60 | + |
| 61 | + - Instructions which ask us to visit a website or download an application, |
| 62 | + even if it is _completely_ open source (and expecially if it is not) |
| 63 | + - Instructions which just describe how to create a project, e.g. with a |
| 64 | + specific build tool or template |
| 65 | + - Screenshots of exceptions |
| 66 | + - Screenshots of code |
| 67 | + - Code snippets copied from a larger application context |
13 | 68 |
|
14 | 69 | ### Expected Result: |
15 | | -...description of what you expected to see... |
| 70 | + |
| 71 | +Describe what you expected to see. If you are reporting a UX/UI error, this may |
| 72 | +include screenshots with annotations. |
16 | 73 |
|
17 | 74 | ### Actual Result: |
18 | | -...what actually happened, including full exceptions (please include the entire stack trace, including "caused by" entries), log entries, screen shots etc. where appropriate... |
| 75 | + |
| 76 | +Describe what actually happened, with special attention to the errant behavior. |
| 77 | +Always include: |
| 78 | + |
| 79 | +- OS and version |
| 80 | +- Platform/language + version |
| 81 | + |
| 82 | +If you are reporting a UX/UI error: |
| 83 | + |
| 84 | +- (if websocket) Platform/language + version of remote perspective server. |
| 85 | +- Full exception/error message if applicable. |
| 86 | +- Any potentially relevent JavaScript developer console error logs. |
| 87 | +- Screenshots of the UI in an obviously broken state. (but please try to avoid |
| 88 | + screenshots of your code, see below) |
| 89 | + |
| 90 | +If you are reporting a library error: |
| 91 | + |
| 92 | +- (if websocket) Platform/language + version of remote perspective server. |
| 93 | +- Full exception error capture (please include the entire stack trace, |
| 94 | + including "caused by" entries), log entries, etc. where appropriate. Please |
| 95 | + avoid posting screenshots of code (which we may need to debug). |
| 96 | + |
| 97 | +If you are reporting a build or install error: |
| 98 | + |
| 99 | +- Full error output from running your repro, formatted as a code block (please |
| 100 | + _do not_ include screenshots of build logs). |
19 | 101 |
|
20 | 102 | ### Environment: |
21 | | -...version and build of the project, OS and runtime versions, virtualised environment (if any), etc. ... |
| 103 | + |
| 104 | +For JavaScript (browser): |
| 105 | + |
| 106 | +- `@finos/perspective` version |
| 107 | +- Browser and version |
| 108 | +- OS |
| 109 | +- (if websocket) Language/version/OS of perspective server |
| 110 | + |
| 111 | +For Node.js: |
| 112 | + |
| 113 | +- `node` version |
| 114 | +- OS |
| 115 | + |
| 116 | +For Python |
| 117 | + |
| 118 | +- `python` interpreter version (Only CPython). |
| 119 | +- package manager and version (conda/pip/\*) |
| 120 | + - Are you compiling from an sdist of wheel? |
| 121 | +- Platform and version (Jupyter/tornado/lib/\*) |
| 122 | +- OS |
22 | 123 |
|
23 | 124 | ### Additional Context: |
24 | | -...add any other context about the problem here. If applicable, add screenshots to help explain... |
| 125 | + |
| 126 | +Add any other context about the problem here. |
0 commit comments