vitess.io/vitess@v0.16.2/.github/ISSUE_TEMPLATE/bug_report.yml (about) 1 name: Bug Report 2 description: You're experiencing an issue with Vitess that is different than the documented behavior. 3 title: "Bug Report: " 4 labels: ["Type: Bug", "Needs Triage"] 5 body: 6 - type: textarea 7 id: overview-of-the-issue 8 attributes: 9 label: Overview of the Issue 10 description: A paragraph or two about the issue you're experiencing. 11 placeholder: Tell us what you see! 12 validations: 13 required: true 14 15 - type: textarea 16 id: reproduction-steps 17 attributes: 18 label: Reproduction Steps 19 description: | 20 A paragraph or two about the issue you're experiencing. 21 Example: 22 1. Deploy the following `vschema`: 23 ```javascript 24 { 25 "sharded": true, 26 "vindexes": { 27 "hash": { 28 "type": "hash" 29 }, 30 "tables": { 31 "user": { 32 "column_vindexes": [ 33 { 34 "column": "user_id", 35 "name": "hash" 36 } 37 ] 38 } 39 } 40 } 41 ``` 42 2. Deploy the following `schema`: 43 ```sql 44 create table user(user_id bigint, name varchar(128), primary key(user_id)); 45 ``` 46 3. Run `SELECT...` 47 4. View error 48 validations: 49 required: true 50 51 - type: textarea 52 id: binary-version 53 attributes: 54 label: Binary Version 55 description: | 56 Tell us which version of Vitess you're using. 57 Example: 58 ```sh 59 giaquinti@workspace:~$ vtgate --version 60 Version: a95cf5d (Git branch 'HEAD') built on Fri May 18 16:54:26 PDT 2018 by giaquinti@workspace using go1.10 linux/amd64 61 ``` 62 render: sh 63 validations: 64 required: true 65 66 - type: textarea 67 id: os-and-env 68 attributes: 69 label: Operating System and Environment details 70 description: | 71 OS, Architecture, and any other information you can provide about the environment. 72 Example: 73 - Operating system (output of `cat /etc/os-release`) 74 - Kernel version (output of `uname -sr`) 75 - Architecture (output of `uname -m`) 76 render: sh 77 validations: 78 required: true 79 80 - type: textarea 81 id: logs 82 attributes: 83 label: Log Fragments 84 description: Include appropriate log fragments. If the log is longer than a few dozen lines, please include the URL to the gist (https://gist.github.com/) of the log instead of posting it in the issue. This will be automatically formatted into code, so no need for backticks. 85 render: sh