🔭 List of issue and/or pull request templates used by some of the most popular GitHub projects.
Please see CONTRIBUTING for details.
-
JavaScript
-
Java
-
Python
-
CSS
-
PHP
-
Ruby
-
C++
-
C
-
Shell
-
C#
-
Objective-C
-
VimL
-
Go
-
Perl
-
CoffeeScript
-
TeX
-
Swift
-
Scala
-
Lua
-
Clojure
-
Groovy
-
PowerShell
#### FreeCodeCamp Issue template
To Use this Template:
* Fill out what you can
* Delete what you do not fill out
NOTE: ISSUES ARE NOT FOR CODE HELP - Ask for Help at https://gitter.im/FreeCodeCamp/Help
#### Issue Description
* When Issue Happens
* Steps To Reproduce
#### Browser Information
* Browser Name, Version
* Operating System
#### Your Code
```js
If relevant, paste all of your challenge code in here
```
#### Screenshot
## FreeCodeCamp Pull Request template
Please, go through these steps before you submit a PR.
1. Make sure that your PR is not a duplicate.
2. If not, then make sure that:
2.1. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the `fix/` or `feature/` prefixes. Good examples are: `fix/signin-issue` or `feature/issue-templates`.
2.2. You have a descriptive commit message with a short title (first line).
2.3. You have only one commit (if not, [squash](https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/git-rebase#squashing-multiple-commits-into-one) them into one commit).
2.4. `npm test` doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`).
3. **After** these steps, you're ready to open a pull request.
3.1. Your pull request MUST NOT target the `master` branch on FreeCodeCamp's repository. You probably want to target `staging` instead.
3.2. Give a descriptive title to your PR.
3.3. Provide a description of your changes.
3.4. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
IMPORTANT: Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines.
**PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING**
***Note*: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.**
**Do you want to request a *feature* or report a *bug*?**
**What is the current behavior?**
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).**
**What is the expected behavior?**
**What is the motivation / use case for changing the behavior?**
**Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.**
**Other information (e.g. stacktraces, related issues, suggestions how to fix)**
**What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)**
**What is the current behavior? (You can also link to an open issue here)**
**What is the new behavior (if this is a feature change)?**
**Does this PR introduce a breaking change?**
**Please check if the PR fulfills these requirements**
- [ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
**Other information**:
Remember, an issue is not the place to ask questions. You can use [Stack Overflow](http://stackoverflow.com/questions/tagged/meteor) for that, or you may want to start a discussion on the [Meteor forum](https://forums.meteor.com/).
Before you open an issue, please check if a similar issue already exists or has been closed before.
### When reporting a bug, please be sure to include the following:
- [ ] A descriptive title
- [ ] What version of Meteor you're using, and the platform(s) you're running it on
- [ ] What packages or other dependencies you're using
- [ ] The behavior you expect to see, and the actual behavior
- [ ] An *isolated* way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem)
See [here](https://github.com/meteor/meteor/blob/devel/Contributing.md#reporting-a-bug-in-meteor) for more detail on what is expected of a bug report.
### When you open an issue for a feature request, please add as much detail as possible:
- [ ] A descriptive title
- [ ] A description of the problem you're trying to solve, including *why* you think this is a problem
- [ ] An overview of the suggested solution
- [ ] If the feature changes current behavior, reasons why your solution is better
See [here](https://github.com/meteor/meteor/blob/devel/Contributing.md#feature-requests) for more detail on what is expected of a feature request.
### Independent core packages
We've split some packages out of meteor/meteor in order to make it easier for community members to contribute and the MDG team to maintain a slimmer core (this enables us to untie package versions from Meteor releases). Please ensure your issue is opened against the appropriate repository. Packages that have been split from core and their repositories are:
- Blaze: https://github.com/meteor/blaze
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
Always follow the [contribution guidelines](https://github.com/meteor/meteor/blob/devel/Contributing.md) when submitting a pull request. In particular, make sure existing tests still pass, and add tests for all new behavior. When fixing a bug, you may want to add a test to verify the fix.
Hey there and thank you for using React Native!
React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
Do the checklist before filing an issue:
- [ ] Is this something you can **debug and fix**? Send a pull request! Bug fixes and documentation fixes are welcome.
- [ ] Have a usage question? Ask your question on [StackOverflow](http://stackoverflow.com/questions/tagged/react-native). We use StackOverflow for usage question and GitHub for bugs.
- [ ] Have an idea for a feature? Post the feature request on [Product Pains](https://productpains.com/product/react-native/). It has a voting system to surface the important issues. GitHub issues should only be used for bugs.
None of the above, create a bug report
------------------------------------------------------------------
Make sure to add **all the information needed to understand the bug** so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.
- [ ] Provide a **minimal code snippet** / [rnplay](https://rnplay.org/) example that reproduces the bug.
- [ ] Provide **screenshots** where appropriate
- [ ] What's the **version** of React Native you're using?
- [ ] Does this occur on iOS, Android or both?
- [ ] Are you using Mac, Linux or Windows?
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
(You can skip this if you're fixing a typo or adding an app to the Showcase.)
Explain the **motivation** for making this change. What existing problem does the pull request solve?
Prefer **small pull requests**. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.
**Test plan (required)**
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Make sure tests pass on both Travis and Circle CI.
**Code formatting**
Look around. Match the style of the rest of the codebase. See also the simple [style guide](https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md#style-guide).
##### Description of the problem
...
##### Three.js version
- [ ] Dev
- [ ] r75
- [ ] ...
##### Browser
- [x] All of them
- [ ] Chrome
- [ ] Firefox
- [ ] Internet Explorer
##### OS
- [x] All of them
- [ ] Windows
- [ ] Linux
- [ ] Android
- [ ] IOS
##### Hardware Requirements (graphics card, VR Device, ...)
**Note: for support questions, please use one of these channels:**
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
#### Short description of the problem:
#### What behavior are you expecting?
**Steps to reproduce:**
1.
2.
3.
```
insert any relevant code between the above and below backticks
```
**Other information:** (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
**Which Ionic Version?** 1.x or 2.x
**Run `ionic info` from terminal/cmd prompt:** (paste output below)
#### Short description of what this resolves:
#### Changes proposed in this pull request:
-
-
-
**Ionic Version**: 1.x / 2.x
**Fixes**: #
**How can we reproduce this bug?**
1. Step one
2. Step two
3. Step three
**What did you expect to happen?**
**What happened instead?**
**Test case:**
Give us a link to a CodePen or JSFiddle that recreates the issue.
- [CodePen with Foundation 6 and MotionUI](http://codepen.io/rafibomb/pen/xVVGOB)
- [CodePen with Foundation 6, Flexbox grid and MotionUI](http://codepen.io/rafibomb/pen/jqqPra)
Before submitting a pull request, make sure it's targeting the right branch:
- For documentation fixes, use `master`.
- For bug fixes, use `develop`.
- For new features, use the branch for the next minor version, which will be formatted `v6.x`.
If you're fixing a JavaScript issue, it would help to create a new test case under the folder `test/visual/` that recreates the issue and show's that it's been fixed. Run `npm test` to compile the testing folder.
Happy coding! :)
_Thanks for wanting to report an issue you've found in Node.js. Please delete
this text and fill in the template below. If unsure about something, just do as
best as you're able._
_Note that it will be much easier for us to fix the issue if a test case that
reproduces the problem is provided. Ideally this test case should not have any
external dependencies. We understand that it is not always possible to reduce
your code to a small test case, but we would appreciate to have as much data as
possible. Thank you!_
* **Version**: _output of `node -v`_
* **Platform**: _either `uname -a` output, or if Windows, version and 32-bit or
64-bit_
* **Subsystem**: _optional. if known - please specify affected core module name_
### Pull Request check-list
_Please make sure to review and check all of these items:_
- [ ] Does `make -j8 test` (UNIX) or `vcbuild test nosign` (Windows) pass with
this change (including linting)?
- [ ] Is the commit message formatted according to [CONTRIBUTING.md][0]?
- [ ] If this change fixes a bug (or a performance problem), is a regression
test (or a benchmark) included?
- [ ] Is a documentation update included (if this change modifies
existing APIs, or introduces new ones)?
_NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open._
### Affected core subsystem(s)
_Please provide affected core subsystem(s) (like buffer, cluster, crypto, etc)_
[0]: https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#step-3-commit
### Description of change
_Please provide a description of the change here._
Welcome to Ghost's GitHub repo! 👋🎉
Do you need help or have a question? Please come chat in Slack: https://ghost.org/slack 👫. Got an idea for a new feature? Please add it to our wishlist: http://ideas.ghost.org 🌟. Found a bug? Please fill out the sections below... thank you 👍
### Issue Summary
A summary of the issue and the browser/OS environment in which it occurs.
### Steps to Reproduce
1. This is the first step
2. This is the second step, etc.
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
### Technical details:
* Ghost Version:
* Node Version:
* Browser/OS:
* Database:
Got some code for us? Awesome 🎊!
Please include a description of your change & check your PR against this list, thanks!
- [ ] Commit message has a short title & issue references
- [ ] Commits are squashed
- [ ] The build will pass (run `npm test`).
More info can be found by clicking the "guidelines for contributing" link above.
**Elasticsearch version**:
**JVM version**:
**OS version**:
**Description of the problem including expected versus actual behavior**:
**Steps to reproduce**:
1.
2.
3.
**Provide logs (if relevant)**:
**Describe the feature**:
What kind of issue is this?
- [ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow. https://stackoverflow.com/questions/tagged/retrofit
- [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. Here’s an example: https://gist.github.com/swankjesse/6608b4713ad80988cdc9
- [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
What kind of issue is this?
- [ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow. https://stackoverflow.com/questions/tagged/okhttp
- [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. Here’s an example: https://gist.github.com/swankjesse/981fcae102f513eb13ed
- [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
Please ensure you have given all the following requested information in your report.
#### Issue details
_Please provide the details of your issue_
#### Reproduction steps/code
_Please provide the steps to reproduce this issue, or even better, a [SSCCE](http://sscce.org/) that reproduces your issue.
You can find barebones templates [here](https://github.com/libgdx/libgdx/wiki/Getting-help)_
#### Version of LibGDX and/or relevant dependencies
_Please provide the version(s) affected._
#### Stacktrace
```java
//Please provide the stacktrace if applicable
```
#### Please select the affected platforms
- [ ] Android
- [ ] iOS
- [ ] HTML/GWT
- [ ] Windows
- [ ] Linux
- [ ] MacOS
(Please remove this text once you've read and understood it.)
## Contributing
The project is in maintenance mode, meaning, changes are driven by contributed patches.
There is otherwise no active development or roadmap for this project. It is "DIY".
Only proposed changes in the form of a pull request are likely to be acted on, but,
these will be acted on promptly.
### Questions
Questions should be asked on the mailing list:
https://groups.google.com/forum/#!forum/zxing
### Feature Requests
Feature requests are not accepted and will generally be closed.
Feature requests with a pull request may be accepted. When in doubt, discuss on the
mailing list first.
### Bug Reports
Bug reports must have enough detail to understand and reproduce the problem. Inadequate
bug reports will be closed with a request for more information.
Bug reports without an associated pull request are not likely to be addressed, but will be
left open for some time to see if anyone can contribute a solution. However, bug reports
with a pull request are likely to be merged promptly.Welcome and thank you for reporting an issue!
If you don't know how to fix a memory leak in your app, please do not file an issue. Read here: https://github.com/square/leakcanary/#how-do-i-fix-a-memory-leak
Are you sure this issue isn't already reported? Try the search field in https://github.com/square/leakcanary/issues .
^^^^^ PLEASE DELETE EVERYTHING ABOVE, INCLUDING THIS LINE ^^^^^
LeakCanary Version:
```
PASTE HERE ANY STACKTRACE OR OUTPUT FROM LEAKCANARY, IN BETWEEN THE TRIPLE BACKQUOTES. REMOVE THIS LINE <====
```
**Glide Version**:
**Integration libraries**:
**Device/Android Version**:
**Issue details / Repro steps / Use case background**:
**Glide load line / `GlideModule` (if any) / list Adapter code (if any)**:
```java
Glide.with...
```
**Layout XML**:
```xml
## Description
## Motivation and Context
## Why this framework/library/software/resource is awesome?
A few sentences describing the reason.
## Vote for this pull request
Who agrees that this change should be merged could add your reactions (e.g. :+1:) to this pull request.
##### ISSUE TYPE
- Bug Report
- Feature Idea
- Documentation Report
##### ANSIBLE VERSION
```
```
##### CONFIGURATION
##### OS / ENVIRONMENT
##### SUMMARY
##### STEPS TO REPRODUCE
```
```
##### EXPECTED RESULTS
##### ACTUAL RESULTS
```
```
##### ISSUE TYPE
- Feature Pull Request
- New Module Pull Request
- Bugfix Pull Request
- Docs Pull Request
##### ANSIBLE VERSION
```
```
##### SUMMARY
```
```
## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2016.04.05*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [ ] I've **verified** and **I assure** that I'm running youtube-dl **2016.04.05**
### Before submitting an *issue* make sure you have:
- [ ] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [ ] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
$ youtube-dl -v
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.04.05
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: https://www.youtube.com/watch?v=BaW_jenozKc
- Single video: https://youtu.be/BaW_jenozKc
- Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc
---
### Description of your *issue*, suggested solution and other information
Explanation of your *issue* in arbitrary form goes here. Please make sure the [description is worded well enough to be understood](https://github.com/rg3/youtube-dl#is-the-description-of-the-issue-itself-sufficient). Provide as much context and examples as possible.
If work on your *issue* required an account credentials please provide them or explain how one can obtain them.
Please try to adhere to the guidelines below as much as possible when
submitting your issue.
- Verify that your issue is not being currently addressed by other
[issues](https://github.com/scikit-learn/scikit-learn/issues?q=)
or [pull requests](https://github.com/scikit-learn/scikit-learn/pulls?q=).
- If your issue is a usage question or does not potentially require
changes to the codebase to be solved, then
[StackOverflow](http://stackoverflow.com/questions/tagged/scikit-learn)
(using the`[scikit-learn]` tag) or our
[mailing list](https://lists.sourceforge.net/lists/listinfo/scikit-learn-general)
may be a better place to bring it up. For more information, see
[User Questions](http://scikit-learn.org/stable/support.html#user-questions).
If you are submitting a bug issue:
- Please include your operating system type and version number, as well
as your Python, scikit-learn, numpy, and scipy versions. This information
can be found by runnning the following code snippet:
```
import platform; print(platform.platform())
import sys; print("Python", sys.version)
import numpy; print("NumPy", numpy.__version__)
import scipy; print("SciPy", scipy.__version__)
import sklearn; print("Scikit-Learn", sklearn.__version__)
```
- Please be specific about what estimators and/or functions are involved
and the shape of the data, as appropriate; please include a
[reproducible](http://stackoverflow.com/help/mcve) code snippet
or link to a [gist](https://gist.github.com). If an exception is raised,
please provide the traceback.
- Please ensure all code snippets and error messages are formatted in
appropriate code blocks.
See ["Creating and highlighting code blocks"](https://help.github.com/articles/creating-and-highlighting-code-blocks).
If you are submitting an algorithm or feature request:
- Please verify that the algorithm fulfills our
[new algorithm requirements](http://scikit-learn.org/stable/faq.html#can-i-add-this-new-algorithm-that-i-or-someone-else-just-published).
Thanks for contributing! Please delete these guidelines before submitting
your issue.
Please try to adhere to the guidelines below as much as possible when submitting your pull request.
- Please verify that your code satisfies the
[code/documentation quality guidelines](http://scikit-learn.org/stable/developers/contributing.html#coding-guidelines).
- Please prefix the title of your pull request with `[MRG]` if the
contribution is complete and should be subjected to a detailed review.
- Incomplete contributions should be prefixed `[WIP]` to indicate a work
in progress (and changed to `[MRG]` when it matures). WIPs may be useful
to: indicate you are working on something to avoid duplicated work,
request broad review of functionality or API, or seek collaborators.
WIPs often benefit from the inclusion of a
[task list](https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments)
in the PR description.
- Documentation and high-coverage tests are necessary for enhancements to
be accepted.
- If you are adding an enhancement, you may wish to provide evidence for
its benefit with distinguishing examples in the code and benchmarks
in the PR discussion.
- If your pull request addresses an issue, please use the title to describe
the issue and mention the issue number in the pull request description to
ensure a link is created to the original issue.
Please be aware that we are a loose team of volunteers so patience is
necessary; assistance handling other issues is very welcome. We value
all user contributions, no matter how minor they are. If we are slow to
review, either the pull request needs some benchmarking, tinkering,
convincing, etc. or more likely the reviewers are simply busy. In either
case, we ask for your understanding during the review process.
For more information, see
[Why is my PR not getting any attention?](http://scikit-learn.org/dev/faq.html#why-is-my-pull-request-not-getting-any-attention)
Thanks for contributing! Please delete these guidelines before submitting your pull request.
# Issue Prelude
**Please complete these steps and check these boxes (by putting an `x` inside
the brackets) _before_ filing your issue:**
- [ ] I have read and understood YCM's [CONTRIBUTING][cont] document.
- [ ] I have read and understood YCM's [CODE_OF_CONDUCT][code] document.
- [ ] I have read and understood YCM's [README][readme], **especially the
[Frequently Asked Questions][faq] section.**
- [ ] I have searched YCM's issue tracker to find issues similar to the one I'm
about to report and couldn't find an answer to my problem. ([Example Google
search.][search])
- [ ] If filing a bug report, I have included the output of `vim --version`.
- [ ] If filing a bug report, I have included the output of `:YcmDebugInfo`.
- [ ] If filing a bug report, I have included the output of
`:YcmToggleLogs stderr`.
- [ ] If filing a bug report, I have included which OS (including specific OS
version) I am using.
- [ ] If filing a bug report, I have included a minimal test case that reproduces
my issue.
- [ ] **I understand this is an open-source project staffed by volunteers and
that any help I receive is a selfless, heartfelt _gift_ of their free time. I
know I am not entitled to anything and will be polite and courteous.**
- [ ] **I understand my issue may be closed if it becomes obvious I didn't
actually perform all of these steps.**
Thank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.
# Issue Details
[If filing a bug report, please include **a list of steps** that describe how to
reproduce the bug you are experiencing. Also include test code if relevant.]
[cont]: https://github.com/Valloric/YouCompleteMe/blob/master/CONTRIBUTING.md
[code]: https://github.com/Valloric/YouCompleteMe/blob/master/CODE_OF_CONDUCT.md
[readme]: https://github.com/Valloric/YouCompleteMe/blob/master/README.md
[faq]: https://github.com/Valloric/YouCompleteMe/blob/master/README.md#faq
[search]: https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fgithub.com%2FValloric%2FYouCompleteMe%2Fissues%20python%20mac
# PR Prelude
Thank you for working on YCM! :)
**Please complete these steps and check these boxes (by putting an `x` inside
the brackets) _before_ filing your PR:**
- [ ] I have read and understood YCM's [CONTRIBUTING][cont] document.
- [ ] I have read and understood YCM's [CODE_OF_CONDUCT][code] document.
- [ ] I have included tests for the changes in my PR. If not, I have included a
rationale for why I haven't.
- [ ] **I understand my PR may be closed if it becomes obvious I didn't
actually perform all of these steps.**
# Why this change is necessary and useful
[Please explain **in detail** why the changes in this PR are needed.]
[cont]: https://github.com/Valloric/YouCompleteMe/blob/master/CONTRIBUTING.md
[code]: https://github.com/Valloric/YouCompleteMe/blob/master/CODE_OF_CONDUCT.md
Fixes # .
Changes proposed in this pull request:
-
-
-
@getsentry/team
### Description of Issue/Question
### Setup
(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
### Steps to Reproduce Issue
(Include debug logs if possible and relevant.)
### Versions Report
(Provided by running `salt --versions-report`. Please also mention any differences in master/minion versions.)
### What does this PR do?
### What issues does this PR fix or reference?
### Previous Behavior
Remove this section if not relevant
### New Behavior
Remove this section if not relevant
### Tests written?
Yes/No
#### Code Sample, a copy-pastable example if possible
#### Expected Output
#### output of ``pd.show_versions()``
- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] passes ``git diff upstream/master | flake8 --diff``
- [ ] whatsnew entry
## [Title here]
## TL;DR;
[content here]
## Username
[twitter account link or github account link ej: [@tips-js](https://twitter.com/tips_js)]
## Extra
[content here]
## 问题描述
（简明扼要地描述一下问题）
## 产生环境
- **设备：**（手机、平板等移动设备时填写此项）
- **操作系统及版本：**
- **浏览器及版本：**
- **演示地址：**
## 复现步奏
1.
2.
...
| Q | A
| ------------- | ---
| Branch? | "master" for new features / 2.3, 2.7, 2.8 or 3.0 for fixes
| Bug fix? | yes/no
| New feature? | yes/no
| BC breaks? | yes/no
| Deprecations? | yes/no
| Tests pass? | yes/no
| Fixed tickets | comma-separated list of tickets fixed by the PR, if any
| License | MIT
| Doc PR | reference to the documentation PR, if any
### What steps will reproduce the problem?
### What is the expected result?
### What do you get instead?
### Additional info
| Q | A
| ---------------- | ---
| Yii version |
| PHP version |
| Operating system |
| Q | A
| ------------- | ---
| Is bugfix? | yes/no
| New feature? | yes/no
| Breaks BC? | yes/no
| Tests pass? | yes/no
| Fixed issues | comma-separated list of tickets # fixed by the PR, if any
With the following composer.json:
```json
{
...
}
```
When I run this command:
```
composer command -vvv (please include -vvv!)
```
I get this output:
```
```
And I expected this to happen:
This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.
* Platform and Target: YOUR WEB-SERVER, DATABASE AND OTHER RELEVANT INFO AND HOW THE REQUEST IS BEING MADE, HERE.
### What you did
EXPLAIN WHAT YOU DID, PREFERABLY WITH CODE EXAMPLES, HERE.
### Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
### Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use [Stack Overflow](http://stackoverflow.com/questions/tagged/cakephp)
for that or join the #cakephp channel on irc.freenode.net, where we will be more
than happy to help answer your questions.
Before you open an issue, please check if a similar issue already exists or has been closed before.
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
Always follow the [contribution guidelines](https://github.com/cakephp/cakephp/blob/master/.github/CONTRIBUTING.md) when submitting a pull request. In particular, make sure existing tests still pass, and add tests for all new behavior. When fixing a bug, you may want to add a test to verify the fix.
Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:
- [ ] You have read and followed closely the [Wiki](https://github.com/phanan/koel/wiki), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://github.com/phanan/koel/wiki/Troubleshooting)
- [ ] The issue has not been reported before
- [ ] This is not a "how to install on Windows" or "why is my npm messed up" question
- [ ] You're a cool person
All checked? Now also make sure your issue
- [ ] Is associated with a version. Or better yet, a commit.
- [ ] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
- [ ] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
- [ ] Is in English, 因为我不说中文。
DO NOT CREATE NEW ISSUES ON THIS REPOSITORY!
Please create all issues found when running `brew install` at https://github.com/Homebrew/homebrew-core/issues/new
Please create all issues found when running any other `brew` command at https://github.com/Homebrew/brew/issues/new
DO NOT CREATE NEW PULL REQUESTS ON THIS REPOSITORY!
Please create formula pull requests at https://github.com/Homebrew/homebrew-core
Please create core code pull requests at https://github.com/Homebrew/brew
###### What version of Jekyll are you using (`jekyll -v`)?
###### What operating system are you using?
###### What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
###### What did you expect to see?
###### What did you see instead?
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
### Vagrant version
Run `vagrant -v` to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.
### Host operating system
This is the operating system that you run locally.
### Guest operating system
This is the operating system you run in the virtual machine.
### Vagrantfile
```ruby
# Copy-paste your Vagrantfile here
```
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
### Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. Do NOT paste the debug
output in the issue, just paste the link to the Gist.
### Expected behavior
What should have happened?
### Actual behavior
What actually happened?
### Steps to reproduce
1.
2.
3.
### References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
- GH-1234
- ...
##### Instructions
- Look for and complete the section relevant to your submission. Delete the others, including these `Instructions`.
- If [using `cask-repair`](https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md#updating-a-cask), checks are performed automatically and this template won’t show.
- `{{cask_file}}` is used a placeholder to the actual cask you’re submitting/editing (if applicable).
- If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.
### Changes to a cask
#### Editing an existing cask
- [ ] Commit message includes cask’s name (and new version, if applicable).
- [ ] `brew cask audit --download {{cask_file}}` is error-free.
- [ ] `brew cask style --fix {{cask_file}}` left no offenses.
#### Adding a new cask
- [ ] Checked there aren’t open [pull requests](https://github.com/caskroom/homebrew-cask/pulls) for the same cask.
- [ ] Checked there aren’t closed [issues](https://github.com/caskroom/homebrew-cask/issues) where that cask was already refused.
- [ ] When naming the cask, followed the [token reference](https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/token_reference.md).
- [ ] Commit message includes cask’s name.
- [ ] `brew cask audit --download {{cask_file}}` is error-free.
- [ ] `brew cask style --fix {{cask_file}}` left no offenses.
- [ ] `brew cask install {{cask_file}}` worked successfully.
- [ ] `brew cask uninstall {{cask_file}}` worked successfully.
### Changes to the core
- [ ] Followed [hacking.md](https://github.com/caskroom/homebrew-cask/blob/master/doc/development/hacking.md).
> ℹ Please fill out this template when filing an issue.
> All lines beginning with a quotation mark (`>`),
> instruct you with what info we expect.
> Please remove this paragraph.
* [ ] I've read and understood the [*CONTRIBUTING guidelines and have done my best effort to follow](https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md).
# Report
## What did you do?
> ℹ Please replace this with what you did.
> e.g. Run `pod install`
## What did you expected to happen?
> ℹ Please replace this with what you expected to happen.
> e.g. Install all pod dependencies correctly.
## What happened instead?
> ℹ Please replace this with of what happened instead.
> e.g. Pod A is missing the subspec B for target C.
## Podfile
> ℹ Please paste the contents of your Podfile below.
> (e.g. via `cat Podfile | pbcopy`)
> You can remove this hint then.
```ruby
# Paste your Podfile contents HERE.
```
### New Issue Checklist
- [ ] Updated fastlane to the latest version
- [ ] I have read the [Contribution Guidelines](https://github.com/fastlane/fastlane/blob/master/CONTRIBUTING.md)
### Issue Description
##### Complete output when running fastlane, including the stack trace and command used
```
INSERT OUTPUT HERE
```
### Configuration Files
Please copy the complete content of your `Fastfile` and any other configuration files you use below:
Fastfile:
```ruby
# INSERT CONTENT HERE
```
### Environment
fastlane version (fastlane -v):
Do you use bundler, rbenv or rvm?
#### What's in this pull request?
#### Resolved bug number: ([SR-](https://bugs.swift.org/browse/SR-))
* * * *
Before merging this pull request to apple/swift repository:
- [ ] Test pull request on Swift continuous integration.
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
**Smoke Testing**
Platform | Comment
------------ | -------------
All supported platforms | @swift-ci Please smoke test
OS X platform | @swift-ci Please smoke test OS X platform
Linux platform | @swift-ci Please smoke test Linux platform
**Validation Testing**
Platform | Comment
------------ | -------------
All supported platforms | @swift-ci Please test
OS X platform | @swift-ci Please test OS X platform
Linux platform | @swift-ci Please test Linux platform
Note: Only members of the Apple organization can trigger swift-ci.
Read the following before submitting your issue, thank you.
* Use our mailing list to ask questions which don't imply bug or feature request: https://groups.google.com/forum/#!forum/nwjs-general
* State which version are you using
* State which OS version are you running with
* Provide a reproducible case if possible
* Attach the crash dump file if it's a crash: http://docs.nwjs.io/en/latest/For%20Developers/Understanding%20Crash%20Dump/#find-minidump-file
Issues meet the checklist above will be processed before those don't.
* Electron version:
* Operating system:
GitHub issues are for bugs / installation problems / feature requests.
For general support from the community, see [StackOverflow](https://stackoverflow.com/questions/tagged/tensorflow).
To make bugs and feature requests more easy to find and organize, we close issues that are deemed
out of scope for GitHub Issues and point people to StackOverflow.
For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
### Environment info
Operating System:
If installed from binary pip package, provide:
1. Which pip package you installed.
2. The output from python -c "import tensorflow; print(tensorflow.__version__)".
If installed from sources, provide the commit hash:
### Steps to reproduce
1.
2.
3.
### What have you tried?
1.
### Logs or other output that would be helpful
(If logs are large, please upload as attachment).
### HHVM Version
### Standalone code, or other way to reproduce the problem
### Expected result
### Actual result
This is a template helping you to create an issue which can be processes as quickly as possible. Feel free to add additional information or remove not relevant points if you do not need them.
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
### Please state the information for your system
- OpenCV version: 2.4 / 3.x
- Host OS: Linux (Ubuntu 14.04) / Mac OS X 10.11.3 / Windows 10
- *(if needed, only cross-platform builds)* Target OS: host / Android 6.0 / ARM board / Raspberry Pi 2
- *(if needed)* Compiler & CMake: GCC 5.3 & CMake 3.5
### In which part of the OpenCV library you got the issue?
Examples:
- objdetect, highgui, imgproc, cuda, tests
- face recognition, resizing an image, reading an jpg image
### Expected behaviour
### Actual behaviour
### Additional description
### Code example to reproduce the issue / Steps to reproduce the issue
Please try to give a full example which will compile as is.
```
#include "opencv2/core.hpp"
#include
using namespace std;
using namespace cv;
int main()
{
double d[] = { 546,2435,7,4534,23423,3 };
cout << "d = 0x" << reinterpret_cast(d) << endl;
return 0;
}
```
resolves #XXXX
### What does this PR change?
Please add your changes here.
I have:
- [ ] searched open and closed issues for duplicates
- [ ] read https://github.com/WhisperSystems/Signal-Android/wiki/Submitting-useful-bug-reports
----------------------------------------
### Bug description
Describe here the issue that you are experiencing.
### Steps to reproduce
- using hyphens as bullet points
- list the steps
- that reproduce the bug
**Actual result:** Describe here what happens after you run the steps above (i.e. the buggy behaviour)
**Expected result:** Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)
### Screenshots
### Device info
**Device:** Manufacturer Model XVI
**Android version:** 0.0.0
**Signal version:** 0.0.0
### Link to debug log
### First time contributor checklist
- [ ] I have read [how to contribute](https://github.com/WhisperSystems/Signal-Android/blob/master/CONTRIBUTING.md) to this project
- [ ] I have signed the [Contributor Licence Agreement](https://whispersystems.org/cla/)
### Contributor checklist
- [ ] I am following the [Code Style Guidelines](https://github.com/WhisperSystems/Signal-Android/wiki/Code-Style-Guidelines)
- [ ] I have tested my contribution on these devices:
* Device A, Android X.Y.Z
* Device B, Android Z.Y
* Virtual device W, Android Y.Y.Z
- [ ] My contribution is fully baked and ready to be merged as is
- [ ] I have made the choice whether I want the [BitHub reward](https://github.com/WhisperSystems/Signal-Android/wiki/BitHub-Rewards) or not by omitting or adding the word `FREEBIE` in my commit message
----------
### Description
[Please include a short description of the problem here]
### Reproduction Steps:
1. [First Step]
2. [Second Step]
3. [Other Steps...]
### Expected behavior:
[Describe expected behavior here]
### Observed behavior:
[Describe observed behavior here]
### Additional information:
[ Other useful information, such as:
When did this problem start?
Does this happen all the time?
Has anything changed on your system recently?
]
---
Fish version: [from the output of fish --version]
Operating system: [your operating system and how you installed fish e.g. Homebrew, Ubuntu PPA, distribution package]
Terminal or terminal emulator: [e.g. PuTTy, iTerm2, GNOME Terminal, VT220]
Description of problem:
Output of the following commands
- `uname -a`:
- `free -m`:
- `docker version`:
- `docker -D info`:
- `sigil -v`:
- `docker run -ti gliderlabs/herokuish:latest herokuish version`:
- `dokku version`:
- `dokku plugin`:
- `docker inspect CONTAINER_ID` (if applicable):
(BEWARE: `docker inspect` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
- `cat /home/dokku//nginx.conf` (if applicable):
- Link to the exact repository being deployed (if possible/applicable):
- If a deploy is failing or behaving unexpectedly:
- Application name
- The type of application being deployed (node, php, python, ruby, etc.)
- If using buildpacks, which custom buildpacks are in use
- If using a `Dockerfile`, the contents of that file
- If it exists, the contents of your `Procfile`.
- Output of failing dokku commands after running `dokku trace on`
(BEWARE: `trace on` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
Environment details (AWS, VirtualBox, physical, etc.):
How was dokku installed?:
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual Results:
Expected Results:
Additional info:
```
Please paste the output of the following command here: sudo edit-chroot -all
```
#### Please describe your issue:
#### If known, describe the steps to reproduce the issue:
**Version Used**:
**Steps to Reproduce**:
1.
2.
3.
**Expected Behavior**:
**Actual Behavior**:
### What version of PushSharp are you using?
### Describe your issue:
### What are the steps required to reproduce this issue?
### Please provide any Exception Stack Traces
## English
Before you report any bugs, please try [latest build]
(https://github.com/Wox-launcher/Wox/wiki/FAQ-English#how-to-install-latest-build)
from **master** branch.
1. Please specify Wox version
- If you download from Appveyor, please specify **build number** (e.g. 1.2.0.550)
- If you checkout from master/dev branch, please specify **commit number**
2. Please describe the steps to **reproduce** the bug
3. Please provide Windows version
4. Please provide Exception info if you have.
5. Please provide logs from `Wox\Logs` if you have.
6. Please provide screenshot if you have
## 中文 / Chinese
报 bug 之前, 请试一下 **master** 分支的[最新的 build](https://github.com/Wox-launcher/Wox/wiki/FAQ-%E4%B8%AD%E6%96%87#%E5%A6%82%E4%BD%95%E5%AE%89%E8%A3%85%E6%9C%80%E6%96%B0-build).
1. 请提供 Wox 版本
- 如果你是从 Appveyor 下载的，请提供 **build number** (e.g. 1.2.0.550)
- 如果你是从 master/dev branch checkout 的，请提供 **commit number**
2. 请提供如何**重现** bug 的步骤
3. 请提供 Windows 版本
4. 如果有 Exception/Crash Report 的话，请一并提供
5. 如果有 logs （`Wox\Logs`）的话，请一并提供
6. 如果有截图的话，请一并提供
## What steps will reproduce this issue?
_Write problem description here_
### Expected outcome
_Write expected outcome here_
--
### Environment
- MahApps.Metro __v?.?.?__
- Windows __??__
- Visual Studio __20xx__
- .NET Framework __?.?__
## What changed?
_Describe the changes you have made to improve this project._
_Closed issues._
## New issue checklist
- [ ] I have read all of the [`README`](https://github.com/jessesquires/JSQMessagesViewController/blob/develop/README.md), [documentation](http://cocoadocs.org/docsets/JSQMessagesViewController/), and [FAQ](https://github.com/jessesquires/JSQMessagesViewController/blob/develop/Documentation/faq.md).
- [ ] I have reviewed the [contributing guidelines](https://github.com/jessesquires/JSQMessagesViewController/blob/develop/.github/CONTRIBUTING.md). Confirmation: ____
- [ ] I have searched [existing issues](https://github.com/jessesquires/JSQMessagesViewController/issues?q=is%3Aissue+sort%3Acreated-desc) and **this is not a duplicate**.
### General information
- Library version(s):
- iOS version(s):
- Devices/Simulators affected:
- Reproducible in the demo project? (Yes/No):
- Related issues:
## Bug report
#### Expected behavior
> ...
#### Actual behavior
> ...
#### Steps to reproduce
> ...
#### Crash log? Screenshots? Videos? Sample project?
>...
## Question or Feature Request
> ...
## Pull request checklist
- [ ] All tests pass. Demo project builds and runs.
- [ ] I have resolved any merge conflicts.
- [ ] I have followed the [coding style](https://github.com/jessesquires/HowToContribute#style-guidelines), and reviewed the [contributing guidelines](https://github.com/jessesquires/JSQMessagesViewController/blob/develop/.github/CONTRIBUTING.md). Confirmation: ____
#### This fixes issue #___.
## What's in this pull request?
>...
> We LOVE to help with any issues or bugs you have!
>
> **Questions**: If you have questions about how to use Realm, ask on
> [StackOverflow](http://stackoverflow.com/questions/ask?tags=realm).
> We monitor the `realm` tag.
>
> **Feature Request**: Just fill in the first two sections below.
>
> **Bugs**: To help you as fast as possible with an issue please describe your issue
> and the steps you have taken to reproduce it in as many details as possible.
>
> Thanks for helping us help you! :-)
>
> Please remove this line and all above before submitting.
## Goals
What do you want to achieve?
## Expected Results
What did you expected to happen?
## Actual Results
What did happened instead?
e.g. the stack trace of a crash
## Steps to Reproduce
What are steps we can follow to reproduce this issue?
## Code Sample
Provide a code sample or test case that highlights the issue.
If relevant, include your model definitions.
For larger code samples, links to external gists/repositories are preferred.
Alternatively share confidentially via mail to [email protected].
Full Xcode projects that we can compile ourselves are ideal!
## Version of Realm and Tooling
[In the CONTRIBUTING guidelines](https://git.io/vgxJO), you will find a script,
which will help determining these versions.
Realm version: ?
Xcode version: ?
iOS/OSX version: ?
Dependency manager + version: ?
- Neovim version:
- Operating system:
- Terminal emulator:
### Actual behaviour
### Expected behaviour
### Steps to reproduce
#### environment
- vim: ????
- vim-airline: ????
- OS: ????
- terminal: ????
#### actual behavior
????
#### expected behavior
????
### Actual behavior
Write here what's happening ...
### Expected behavior
Write here what you're expecting ...
### Steps to reproduce:
Please create a reproducible case of your problem. Re produce it
with a minimal `vimrc` with all plugins disabled and only `vim-go`
enabled:
1.
2.
3.
### Configuration
Add here your current configuration and additional information that might be
useful, such as:
* `vimrc` you used to reproduce
* vim version:
* vim-go version
* go version
Explain the problem here ...
------------------------------
```
```
- Type:
- [ ] Bug
- [ ] Enhancement
- [ ] Feature Request
- [ ] Question
- OS:
- [ ] All/Other
- [ ] Linux
- [ ] OS X
- [ ] Windows
- Vim:
- [ ] Terminal Vim
- [ ] GVim
- [ ] Neovim
Describe the details of your PR ...
**Output of `docker version`:**
```
(paste your output here)
```
**Output of `docker info`:**
```
(paste your output here)
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**
**Steps to reproduce the issue:**
1.
2.
3.
**Describe the results you received:**
**Describe the results you expected:**
**Additional information you deem important (e.g. issue happens only occasionally):**
**- What I did**
**- How I did it**
**- How to verify it**
**- A picture of a cute animal (not mandatory but encouraged)**
We DO NOT take questions or config/deploy problems on GitHub, please use our forum: https://discuss.gogs.io
Please take a moment to search that an issue doesn't already exist.
For bug reports, please give the relevant info:
- Gogs version (or commit ref):
- Git version:
- Operating system:
- Database:
- [ ] PostgreSQL
- [ ] MySQL
- [ ] SQLite
- Can you reproduce the bug at http://try.gogs.io:
- [ ] Yes (provide example URL)
- [ ] No
- [ ] Not relevant
- Log gist:
## Description
...
Please, make sure you are targeting the `develop` branch!
More instructions about contributing with Gogs code can be found here:
https://github.com/gogits/gogs/wiki/Contributing-Code
Please check if what you want to add to `awesome-go` list meets [quality standards](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standard) before sending pull request. Thanks!
Please provide package links to:
- godoc.org:
- goreportcard.com:
- gocover.io:
Note, that new categories can be added only when there are 3 packages or more.
Make shure that you've checked the boxes below before you submit PR:
- [ ] I have added my package in alphabetical order
- [ ] I know that this package was not listed before
- [ ] I have added godoc link
- [ ] I have added gocover.io link
- [ ] I have added goreportcard link
- [ ] I have read [Contribution guidelines](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#contribution-guidelines) and [Quality standard](https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standard).
Thanks for your PR, you're awesome :+1:
If your issue is a support request ("How do I get my devices to connect?"
or similar), please use the support forum at https://forum.syncthing.net/
where a large number of helpful people hang out. This issue tracker is for
reporting bugs or feature requests directly to the developers.
If your issue is a bug report, replace this boilerplate with a description
of the problem, being sure to include at least:
- what happened,
- what you expected to happen instead, and
- any steps to reproduce the problem.
Also fill out the version information below and add log output or
screenshots as appropriate.
If your issue is a feature request, simply replace this template text in
its entirety.
### Version Information
Syncthing Version: v0.x.y
OS Version: Windows 7 / Ubuntu 14.04 / ...
Browser Version: (if applicable, for GUI issues)
### Purpose
Describe the purpose of this change. If there is an existing issue that is
resolved by this pull request, ensure that the commit subject is on the form
`Some short description (fixes #1234)` where 1234 is the issue number.
### Testing
Describe what testing has been done, and how the reviewer can test the change
if new tests are not included.
### Screenshots
If this is a GUI change, include screenshots of the change. If not, please
feel free to just delete this section.
### Documentation
If this is a user visible change (including API and protocol changes), add a link here
to the corresponding pull request on https://github.com/syncthing/docs or describe
the documentation changes necessary.
### Authorship
Every author of a code contribution (Go, Javascript, HTML, CSS etc, with the
possible exception of minor typo corrections and similar) is recorded in the
AUTHORS and NICKS files and the in-GUI credits. If this is your first
contribution, a maintainer will add you properly before accepting the
contribution. You need not do so yourself or worry about the fact that the
"authors" automated test fails. However, if your name (such as you want it
presented in the credits) is not visible on your Github profile or in your
commit messages, please assist by providing it here.
Thank you! For helping us make Grafana even better.
To help us respond to your issues faster, please make sure to add as much information as possible.
If this issue is about a plugin, please open the issue in that repository.
Start your issues title with [Feature Request] / [Bug] / [Question] or no tag if your unsure.
Ex
* What grafana version are you using?
* What datasource are you using?
* What OS are you running grafana on?
* Link the PR to an issue for new features
* Rebase your PR if it gets out of sync with master
### Directions
_GitHub Issues are reserved for actionable bug reports and feature requests._
_General questions should be sent to the [InfluxDB mailing list](https://groups.google.com/forum/#!forum/influxdb)._
_Before opening an issue, search for similar bug reports or feature requests on GitHub Issues._
_If no similar issue can be found, fill out either the "Bug Report" or the "Feature Request" section below.
_Erase the other section and everything on and above this line._
### Bug report
__System info:__ [Include InfluxDB version, operating system name, and other relevant details]
__Steps to reproduce:__
1. [First Step]
2. [Second Step]
3. [and so on...]
__Expected behavior:__ [What you expected to happen]
__Actual behavior:__ [What actually happened]
__Additional info:__ [Include gist of relevant config, logs, etc.]
*Please note, the quickest way to fix a bug is to open a Pull Request.*
### Feature Request
Opening a feature request kicks off a discussion.
Requests may be closed if we're not actively planning to work on them.
__Proposal:__ [Description of the feature]
__Current behavior:__ [What currently happens]
__Desired behavior:__ [What you would like to happen]
__Use case:__ [Why is this important (helps with prioritizing requests)]
###### Required for all non-trivial PRs
- [ ] Rebased/mergable
- [ ] Tests pass
- [ ] CHANGELOG.md updated
- [ ] Sign [CLA](https://influxdata.com/community/cla/) (if not already signed)
###### Required only if applicable
_You can erase any checkboxes below this note if they are not applicable to your Pull Request._
- [ ] [InfluxQL Spec](https://github.com/influxdata/influxdb/blob/master/influxql/README.md) updated
Please answer these questions **for each node in your cluster**:
1. What version of CockroachDB are you using (`cockroach version`)?
2. What operating system and processor architecture are you using?
3. What flags/environment variables did you pass to `cockroach start`?
Please describe the issue you observed:
1. What did you do?
2. What did you expect to see?
3. What did you see instead?
Thank you for taking the time to use Drone and file an issue or feature request. Before filing an issue please ensure the following boxes are checked, if applicable:
- [ ] I have searched for existing issues
- [ ] I have discussed the issue with the community at https://gitter.im/drone/drone
- [ ] I have provided a sample `.drone.yml` file to help the team reproduce
- [ ] I have provided details from the build logs
- [ ] I have provided details from the server logs by running `docker logs drone`
- [ ] I am not using the issue tracker to ask why my build failed
**DELETE THIS TEMPLATE BEFORE SUBMITTING**
If you are planning to open a pull-request just open the pull-request instead of making an issue first.
FOR FEATURES:
Describe the feature you want and your use case _clearly_.
FOR BUGS:
Describe the problem and include the following information:
- Packer Version
- Host platform
- Debug log output from `PACKER_LOG=1 packer build template.json`.
Please paste this in a gist https://gist.github.com
- The _simplest example template and scripts_ needed to reproduce the bug.
Include these in your gist https://gist.github.com
**DELETE THIS TEMPLATE BEFORE SUBMITTING**
Describe the change you are making here!
Please include tests. Check out these examples:
- https://github.com/mitchellh/packer/blob/master/builder/virtualbox/common/ssh_config_test.go#L19-L37
- https://github.com/mitchellh/packer/blob/master/post-processor/compress/post-processor_test.go#L153-L182
If your PR resolves any open issue(s), please indicate them like this so they will be closed when your PR is merged:
Closes #xxx
Closes #xxx
### Version
_Version of Slic3r used goes here_
_Use `About->About Slic3r` for release versions_
_For -dev versions, use `git describe --tag` or get the hash value for the version you downloaded or `git rev-parse HEAD`_
### Operating system type + version
_What OS are you using, and state any version #s_
### Behavior
* _Describe the problem_
* _Steps needed to reproduce the problem_
* _If this is a command-line slicing issue, include the options used_
* _Expected Results_
* _Actual Results_
* _Screenshots from __*Slic3r*__ preview are preferred_
_Is this a new feature request?_
#### STL/Config (.ZIP) where problem occurs
_Upload a zipped copy of an STL and your config (`File -> Export Config`)_
(Thanks for reporting an issue! Please make sure you click the link above to view the issue guidelines, then fill out the blanks below.)
What are the steps to reproduce this issue?
-------------------------------------------
1. …
2. …
3. …
What happens?
-------------
…
What were you expecting to happen?
----------------------------------
…
Any logs, error output, etc?
----------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Any other comments?
-------------------
…
What versions of software are you using?
----------------------------------------
**Operating System:** …
**Toolchain Version:** …
**SDK Version:** …
(Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.)
What does this implement/fix? Explain your changes.
---------------------------------------------------
…
Does this close any currently open issues?
------------------------------------------
…
Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Any other comments?
-------------------
…
Where has this been tested?
---------------------------
**Operating System:** …
**Platform:** …
**Target Platform:** …
**Toolchain Version:** …
**SDK Version:** …
### Prerequisites
* [ ] Can you reproduce the problem in [safe mode](http://flight-manual.atom.io/hacking-atom/sections/debugging/#check-if-the-problem-shows-up-in-safe-mode)?
* [ ] Are you running the [latest version of Atom](http://flight-manual.atom.io/hacking-atom/sections/debugging/#update-to-the-latest-version)?
* [ ] Did you check the [debugging guide](flight-manual.atom.io/hacking-atom/sections/debugging/)?
* [ ] Did you check the [FAQs on Discuss](https://discuss.atom.io/c/faq)?
* [ ] Are you reporting to the [correct repository](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#atom-and-packages)?
* [ ] Did you [perform a cursory search](https://github.com/issues?q=is%3Aissue+user%3Aatom+-repo%3Aatom%2Felectron) to see if your bug or enhancement is already reported?
For more information on how to write a good [bug report](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-bug-report) or [enhancement request](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-enhancement-suggestion), see the `CONTRIBUTING` guide.
### Description
[Description of the bug or feature]
### Steps to Reproduce
1. [First Step]
2. [Second Step]
3. [and so on...]
**Expected behavior:** [What you expected to happen]
**Actual behavior:** [What actually happened]
### Versions
You can get this information from executing `atom --version` and `apm --version` at the command line. Also, please include the OS and what version of the OS you're running.
##### Are there any related issues?
...
##### What operating system are you using?
...
##### What version of N1 are you using?
...
--
**Bug?**
##### Do you have any third-party plugins installed?
...
##### Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
...
##### Is the issue reproducible with a particular attachment, message, signature, etc?
...
--
**Feature Request?**
##### Does this feature exist in another mail client or tool you use?
...
Your Rocket.Chat version: (make sure you are running the latest)
@RocketChat/core
Closes #ISSUE_NUMBER
- [ ] PR touches only one file (or a set of logically related files with similar changes made)
- [ ] Content changes are aimed at *intermediate to experienced programmers* (this is a poor format for explaining fundamental programming concepts)
- [ ] YAML Frontmatter formatted according to [CONTRIBUTING.md](https://github.com/adambard/learnxinyminutes-docs/blob/master/CONTRIBUTING.markdown)
- [ ] Seriously, look at it now. Watch for quotes and double-check field names.
## Description
## Checklist:
- [ ] Tests passed.
* `carthage version`:
* `xcodebuild -version`:
* Are you using `--no-build`?
* Are you using `--no-use-binaries`?
* Are you using `--use-submodules`?
**Cartfile**
```
```
**Carthage Output**
```
```
### New Issue Checklist
* [ ] I have looked at the [Documentation](http://snapkit.io/docs)
* [ ] I have read the [F.A.Q.](http://snapkit.io/faq)
### Issue Info
Info | Value |
-------------------------|-------------------------------------|
Platform | e.g. ios/osx/tvos
Platform Version | e.g. 8.0
SnapKit Version | e.g. 0.19.0
Integration Method | e.g. carthage/cocoapods/manually
### Issue Description
### Are you looking for help?
This is an issue tracker, used to manage and track the development of Play. It is not a support system and so it is not a place to ask questions or get help. If you're not sure if you have found a bug, the best place to start is with either the [users mailing list](https://groups.google.com/forum/#!forum/play-framework) or [Stack Overflow](http://stackoverflow.com/questions/ask?tags=playframework). If you have a feature request, the [developer mailing list](https://groups.google.com/forum/#!forum/play-framework-dev) is a better forum than an issue tracker to discuss it.
### Play Version (2.5.x / etc)
### API (Scala / Java / Neither / Both)
### Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
Use `uname -a` if on Linux.
### JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)
Paste the output from `java -version` at the command line.
### Library Dependencies
If this is an issue that involves integration with another system, include the exact version and OS of the other system, including any intermediate drivers or APIs i.e. if you connect to a PostgreSQL database, include both the version / OS of PostgreSQL and the JDBC driver version used to connect to the database.
### Expected Behavior
Please describe the expected behavior of the issue, starting from the first action.
1.
2.
3.
### Actual Behavior
Please provide a description of what actually happens, working from the same starting point.
Be descriptive: "it doesn't work" does not describe what the behavior actually is -- instead, say "the page renders a 500 error code with no body content." Copy and paste logs, and include any URLs. Turn on internal Play logging with `` if there is no log output.
1.
2.
3.
### Reproducible Test Case
Please provide a PR with a failing test.
If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.
# Pull Request Checklist
* [ ] Have you read [How to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request)?
* [ ] Have you read through the [contributor guidelines](https://www.playframework.com/contributing)?
* [ ] Have you signed the [Lightbend CLA](https://www.lightbend.com/contribute/cla)?
* [ ] Have you [squashed your commits](https://www.playframework.com/documentation/2.4.x/WorkingWithGit#Squashing-commits)?
* [ ] Have you added copyright headers to new files?
* [ ] Have you checked that both Scala and Java APIs are updated?
* [ ] Have you updated the documentation for both Scala and Java sections?
* [ ] Have you added tests for any changed functionality?
## Fixes
Fixes #xxxx
## Purpose
What does this PR do?
## Background Context
Why did you take this approach?
## References
Are there any relevant issues / PRs / mailing lists discussions?
### Before submitting an issue to Gitbucket I have first:
- [] read the [contribution guidelines](https://github.com/gitbucket/gitbucket/blob/master/.github/CONTRIBUTING.md)
- [] searched for similar already existing issue
- [] read the documentation and [wiki](https://github.com/gitbucket/gitbucket/wiki)
*(if you have performed all the above, remove the paragraph and continue describing the issue with template below)*
## Issue
**Impacted version**: xxxx
**Deployment mode**: *explain here how you use gitbucket : standalone app, under webcontainer (which one), with an http frontend (nginx, httpd, ...)*
**Problem description**:
- *be as explicit has you can*
- *describe the problem and its symptoms*
- *explain how to reproduce*
- *attach whatever information that can help understanding the context (screen capture, log files)*
- *do your best to use a correct english (re-read yourself)*
### Before submitting a pull-request to Gitbucket I have first:
- [] read the [contribution guidelines](https://github.com/gitbucket/gitbucket/blob/master/.github/CONTRIBUTING.md)
- [] rebased my branch over master
- [] verified that project is compiling
- [] verified that tests are passing
- [] squashed my commits as appropriate *(keep several commits if it is relevant to understand the PR)*
- [] [marked as closed](https://help.github.com/articles/closing-issues-via-commit-messages/) all issue ID that this PR should correct
Problem
Explain the context and why you're making that change. What is the
problem you're trying to solve? In some cases there is not a problem
and this can be thought of being the motivation for your change.
Solution
Describe the modifications you've done.
Result
What will change as a result of your pull request? Note that sometimes
this section is unnecessary because it is self-explanatory based on
the solution.
(See the guidelines for contributing, linked above)
## steps
## problem
## expectation
## notes
(See the guidelines for contributing, linked above)
### Context of the issue.
[Provide more detailed introduction to the issue itself and why it is relevant]
### Expected behavior.
[Describe what you would expect to have resulted from this process.]
### Actual behavior.
[Describe what you currently experience from this process, and thereby explain the bug.]
### Steps to reproduce.
[Present a minimal example and steps to produce the issue.]
### OS and hardware information.
+ Operating system: [todo]
+ Torch version: [todo]
+ CPU architecture: [todo]
+ GPU type (if using): [todo]
### What does this PR do?
### Where should the reviewer start?
### How should this PR be tested?
### Any background context you want to provide?
### What are the relevant issues?
[You can link directly to issues by entering # then the
number of the issue, for example, #3 links to issue 3]
# Screenshots (if appropriate)
# Questions:
+ Do the docs need to be updated?
+ Does this PR add new (Python) dependencies?
* KOReader version:
* Device:
#### Issue
#### Steps to reproduce
#### Describe the issue
#### Steps to Reproduce
1. *Load save game attached to this ticket*
2.
3.
#### Save Game
*It is often useful for us if you have a save game from shortly before the
issue occurs that can be used to recreate the problem. Sometimes a save that
shows the issue happening may be useful as well. As GitHub currently only
supports uploading of images, you will have to upload your your savegames to
an another source such as [Google Drive](https://drive.google.com),
[Dropbox](https://dropbox.com), or
[SkyDrive/OneDrive](https://onedrive.live.com). Add the link to the file to
your issue and make the file(s) public, so we can access your gamelog or
savegame. The most important thing is to not remove these files after you
uploaded them!*
#### Expected Behavior
#### System Information
**CorsixTH Version:** *e.g. 0.50 or 7d886f35ca*
**Operating System:** *e.g. Windows 10*
**Theme Hospital Version:** *CD, GOG.com, Origin, or Demo*
#### Gamelog.txt
*For information about where to find gamelog.txt see:
https://github.com/CorsixTH/CorsixTH/wiki/Frequently-Asked-Questions#where-do-i-find-the-configuration-or-the-gamelog-file*
```
Paste gamelog.txt output here
```
### Additional Info
*Paste any screen shots or other additional information that might help
illustrate the problem.*
If this is a bug report, please fill in the blanks:
* I am using the ___________ browser.
* My computer's OS is ___________.
* I'm running Metabase ___________. [locally from the JAR / locally with the Mac App / on AWS / on Herkou / etc.]
* My database is ___________.
* My Metabase version is ___________.
Before we can merge your pull request, you'll need to sign our [Contributor License Agreement](https://docs.google.com/a/metabase.com/forms/d/1oV38o7b9ONFSwuzwmERRMi9SYrhYeOrkbmNaq9pOJ_E/viewform)
(unless it's a tiny documentation change). Fill this out when you get a chance, and let us know in the PR! :100:
Please take the time to search the repository, if your question has already been asked or answered.
- [ ] What version of the library are you using? Is it the latest version? The latest released version is [  ](https://bintray.com/springfox/maven-repo/springfox/_latestVersion)
What kind of issue is this?
- [ ] Question. Is this a question about how to do a certain thing?
- [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests or
steps to reproduce get fixed faster. Here’s an example: https://gist.github.com/swankjesse/6608b4713ad80988cdc9
- [ ] spring xml/java config that is relevant
- [ ] springfox specific configuration if it makes sense
- [ ] include any output you've received; logs, json snippets etc.; and what the expected output should be
- [ ] if you have a repo that demonstrates the issue for bonus points! See [this example](https://github.com/springfox/springfox/issues/494)
- [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
#### What's this PR do/fix?
#### Are there unit tests? If not how should this be manually tested?
#### Any background context you want to provide?
#### What are the relevant issues?
What kind of issue is this?
- [ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use [Stack
Overflow](https://stackoverflow.com/questions/tagged/groovy-android) with the android-groovy tag.
- [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. See [here](https://github.com/groovy/groovy-android-gradle-plugin/tree/master/gradle-groovy-android-plugin/src/test/groovy/groovyx/grooid)
for some example tests.
- [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.
## Empire Version
## OS Information (Linux flavor, Python version)
## Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
## Screenshot of error, embedded text output, or Pastebin link to the error
## Any additional information
Last updated on: 2016-04-06 13:26:23