Reporting Bugs

Do you have a bug you're facing? Report it! Feel free to voice you concerns via the issue-tracker on GitHub.

Before Submitting

Before submitting a issue make sure you:

• Are using the latest version of XSRFProbe.
• Have installed the dependencies using pip3 instead of pip.
• Have read the documentation before submitting this issue.

How to Submit Bugs:

Avoid Duplicates

A tactic is to simply glance at the most recent bugs, especially if you suspect this a new bug in a process you're sure used to work before. You also might find a bug that's been rejected or closed. In these cases, the problem is usually something external to XSRFProbe -- user error, configuration weirdness, local dependency error, etc.

Full Description

You bug report should have the all basics - a short but descriptive title, a full backtrace of the error, a complete history of how you got there, and version information. This kind of bugs are very search-friendly also.

Your Environment

It may be that the bug you're describing only comes up in your environment. The output of the commands python -v, and uname -a is usually very helpful in understanding and analysing the error.

Reproduction Steps

When you are issuing a new pull request, make sure you are giving the steps for the proper reproduction of the error, eg. a list of arguments which you had supplied to XSRFProbe, the url, and the values of the parameter passed are specially helpful.

Potential Cause/Fix

Maybe you've run into a bug, and you already know how to fix it. Or, you're just a kind stranger on the Internet who wants to help out. Please do mention the probable fix/cause which will help in speeding up the evaluation process.