-
Notifications
You must be signed in to change notification settings - Fork 4
Bug reports
If you were linked to this page from Github Issues Tracker, don't worry! We still love you and want your feedback, but you may have left some important information out of your report. Please read below.
First off: if you have questions about CSV_Record, please search the Wiki to see if your questions have already been answered. If not, feel free to contact us. Do not use the GitHub Issues tracker for questions
- Before submitting a bug report:
Ensure you are using latest devise version. If you are using Devise from git repository with bundler, be sure to run bundle update. Maybe your error was already fixed. Search the existing GitHub Issues to make sure your issue hasn't already been reported. If not, proceed.
- When submitting a bug report:
Include Ruby, CSV_Record and Rails (if using Rails) versions in the report; Include error class, message and backtrace if you are getting an error;
- The information above can help us spot an obvious bug, however most bugs may require you to investigate deeper. In such cases:
Please try to reproduce the bug in CSV_Record test suite. CSV_Record test suite is a Ruby application as any other (check test/csv_record in the repository) making it easy to reproduce bugs; Or try to isolate the bug in a smaller application and push it to github; Remember that this is an open-source project, and the contributions of volunteers have made it possible. Please be polite and provide as much information as possible so that we can help you!
- Our Issues Tracker is available here: