This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 67
Filing new issues or bugs
alshabib edited this page Feb 7, 2013
·
1 revision
If you have found a bug and you want to report it, report it at the FlowVisor issue tracker.
- Click NEW ISSUE button
- IMPORTANT Enter short but descriptive title. It allows to easily identify what the bug report is about.
- Fill the description box explaining a few important details:
- What is the problem - what is happening?
- What is the expected behaviour - what should be happening?
- IMPORTANT What steps are necessary to reproduce the problem? It is essential to sort out the problem quickly.
- What is FlowVisor version you are using?
- What is distribution and/or OS version?
- Did you obtain FlowVisor as a binary or directly from source?
- IMPORTANT We recommend to format the description using GitHub Flavoured Markdown syntax. This makes the bug report clear and readable, especially if you want to include blocks with source code and command line output or auto-link to GitHub references like commits (SHA1) or other issues.
- If you want to attach a patch, git diff output or a very long log file, use Gist service:
- Paste your content
- It is a good idea to fill Gist description and name the file
- IMPORTANT Click Create Public Gist
- Then copy and paste URL of your Gist into the issue description.
- System Requirements
- XML-RPC Deprecated
- Installation
- FlowVisor FAQ
- CLI User Guide
- Papers
-
Development
- Design Documents
-
Architecture
- IO Overview
- Actions
- Messages
- Configuration Parameters
- Processes
- RoadMap