Bug Reports and Feature Requests
Bug reports and feature requests for Cordelia, Kent and antonio all go to one tracker: GitHub Issues on the antonio repository. Search there before filing, to see whether something has already been reported and to follow along on anything you've submitted. The form asks which application you're writing about.
If you don't have a GitHub account
Email help@venholaconsulting.ca instead. Mention which application you're writing about, and whether you're reporting a bug or requesting a feature.
What to include for Cordelia
Include a copy of the console output if you have
it (see its Copy all button), along with your version number, shown in
About Cordelia. If you can open a terminal, the output of cordelia --devinfo
is better still: it names the exact build of Cordelia and of every library in it. See
About Cordelia.
What to include for Kent
Include the exact command you ran, the full output, and the exit code
(echo $? straight afterward). Kent prints its messages, error messages included, on standard
output, so kent info mydata.sqlite > out.txt 2>&1 captures everything;
the standard-error redirect catches the one exception, an unhandled-exception message, which
is the only thing Kent sends there. Include your version number
too. See Getting Help and Version Information.
If the report involves a specific database, kent
details's output describes it (schema version, table counts, file size) without
exposing any of the data in it.
Source repositories
antonio's repository is public. It holds the example report scripts, and it hosts the tracker for all three applications. Cordelia's and Kent's own repositories stay private (see Contributing to the Project), so their code and commit history aren't publicly browsable, but you don't need access to either one to file a report.