Examples of Bugging in the following topics:
-
- This document tells how and where to report bugs.
- You may also file a bug report at http://httpd.apache.org/bug_report.html.
- * If the bug is in your rug, please give it a hug and keep it snug.
- First, make sure it's a bug.
- with a clear description of what the bug is.
-
- The same goes for the project's bug tracker.
- A project with a large and well-maintained bug database (meaning bugs are responded to promptly, duplicate bugs are unified, etc.) therefore makes a better impression than a project with no bug database, or a nearly empty database.
- Of course, if your project is just getting started, then the bug database will contain very few bugs, and there's not much you can do about that.
- Note that bug trackers are often used to track not only software bugs, but enhancement requests, documentation changes, pending tasks, and more.
- The details of running a bug tracker are covered in the section called "Bug Tracker" in Technical Infrastructure, so I won't go into them here.
-
- Handling a security vulnerability is different from handling any other kind of bug report.
- Every step of the standard bug-handling process is visible to all who care to watch: the arrival of the initial report, the ensuing discussion, and the eventual fix.
- Security bugs are different.
- To discuss such a problem openly would be to advertise its existence to the entire world—including to all the parties who might make malicious use of the bug.
- Don't talk about the bug publicly until a fix is available; then supply the fix at exactly the same moment you announce the bug.
-
- Chagas disease is caused by the protozoan parasite Trypanosoma cruzi and transmitted via the reduviid bug.
- It is transmitted to humans via the reduviid bug (the "kissing bugs"), and is therefore characterized as a zoonotic disease.
- The bugs are nocturnal, emerge at night and typically feed on an individual's face.
- In Chagas-endemic areas, the main mode of transmission is through an insect vector called a triatomine or reduviid bug.The bugs emerge at night, when the inhabitants are sleeping.
- Because they tend to feed on people's faces, triatomine bugs are also known as "kissing bugs."
-
- No matter what bug tracker a project uses, some developers always like to complain about it.
- This seems to be more true of bug trackers than of any other standard development tool.
- It's somewhat more than a bug tracker, since it also offers wikis, message forums, and other features, but bug-tracking seems to be the core of what it does.
- Trac is a bit more than a bug tracker: it's really an integrated wiki and bug tracking system.
- Flyspray is a web-based bug tracking system written in PHP.
-
- Bug tracking is a broad topic; various aspects of it are discussed throughout this book.
- The term bug tracker is misleading.
- The bug gets reproduced.
- But most filings are for genuine bugs, so we'll focus on that here. )
- Scheduling may also be dispensed with, if the bug is quick to fix.6.
-
- The first step in combatting this trend is usually to put a prominent notice on the front page of the bug tracker, explaining how to tell if a bug is really a bug, how to search to see if it's already been reported, and finally, how to effectively report it if one still thinks it's a new bug.
- The two things that will do the most to prevent this problem are: making sure there are people watching the bug tracker who have enough knowledge to close tickets as invalid or duplicates the moment they come in, and requiring (or strongly encouraging) users to confirm their bugs with other people before filing them in the tracker.
- Sometimes the second party is able to identify that the behavior is not a bug, or is fixed in recent releases.
- Often it's enough just to ask the user "Did you search the bug tracker to see if it's already been reported?
- The only way to prevent misfilings entirely is to close off the bug tracker to everyone but developers—a cure that is almost always worse than the disease.
-
- For example, the company may use a different bug tracker than the public project.
- Furthermore, when they discover a bug with an easy workaround, they often silently implement the workaround without bothering to report the bug.
- Such reports would be inappropriate for the public bug tracker, both because of their form and because of confidentiality concerns.
- Yet the core bug report itself is important to the public.
- Maintaining two tickets for one bug is, naturally, more work than maintaining one ticket.
-
- Projects are prepared to receive reports of bugs found in released versions, and bugs found in recent trunk and major branch code (that is, found by people who deliberately run bleeding edge code).
- When a bug report comes in from these sources, the responder will often be able to confirm that the bug is known to be present in that snapshot, and perhaps that it has since been fixed and that the user should upgrade or wait for the next release.
- If it is a previously unknown bug, having the precise release makes it easier to reproduce and easier to categorize in the tracker.
- Projects are not prepared, however, to receive bug reports based on unspecified intermediate or hybrid versions.
- I have even seen dismayingly large amounts of time wasted because a bug was absent when it should have been present: someone was running a slightly patched up version, based on (but not identical to) an official release, and when the predicted bug did not happen, everyone had to dig around a lot to figure out why.
-
- Obviously, a project needs the ability to receive security bug reports from anyone.
- But the regular bug reporting address won't do, because it can be watched by anyone too.
- Therefore, have a separate mailing list for receiving security bug reports.
- This is the group that will handle security bugs.