{(sk:page-preamble "Reporting a bug in Yenta" "icon-help" "Help")}

# Have you found a bug?

If Yenta tells you that it has detected an internal error, that is a bug.

If Yenta ever exits without you telling it to, and you're sure that you or the superuser did not kill it, then that is a bug. (Note that Yenta runs in the background, and will not show up to just the "jobs" command in the shell; you'll need to use "ps" with the appropriate arguments for your operating system to see if your Yenta is still running.)

If Yenta apparently takes "forever" to complete some action, that is probably a bug. If it is scanning a very large document set, it may take substantian time to complete this action. But if Yenta is not scanning documents, and yet it becomes unresponsive to commands (for example, clicking on a link never gives you a new page), then that is a bug. [If your browser does not complain that "the site is down," but simply hangs, then Yenta is at least still running. If your browser claims "the site is down," immediately, when you click on a link, then Yenta has crashed and exited.]

If a command does the wrong thing, that is a bug. But be sure you know for certain what it ought to have done. If you aren't familiar with the command, or don't know for certain how the command is supposed to work, then it might actually be working right. Rather than jumping to conclusions, show the problem to someone who knows for certain.

If the documentation for a command does not describe what it seems to do, then this is a bug: the command and its documentation should agree. [Note, however, that this Alpha-test Yenta is missing a great deal of documentation.]

[Bug reporting in general | The most useful way to report a bug]

{(sk:page-postamble)}