Section 7.4. Reporting Mongrel Bugs

7.4. Reporting Mongrel Bugs

Sometimes Mongrel has defects that you would like to report. This is difficult, though, because many problems aren't only Mongrel's, but usually with Mongrel and some Web framework being hosted. Add to this the potential that your code may be broken and debugging gets tougher. What you need to do when submitting a potential defect to Mongrel is to follow this process as best you can:

  1. Make sure the defect isn't already reported on the mailing list or the bug tracker.

  2. Reduce the bug to the simplest code and procedure that demonstrates it. Many times just doing this will help you find any problems and fix them yourself.

  3. If after reducing the bug you find it's actually a Mongrel defect, post a report to the bug Tracker.

  4. Be sure to include the versions of all the software you use, your reduced code, and the test procedure.

  5. Wait for it to be fixed. Usually defects are fixed in one version and quite quickly.

  6. If you can submit a patch that fixes it, then that's great. Make sure the patch is against the release you're using so we can validate it.

Zed Sez

I'm not a porn star. I know, I look like one, but I'm not. Yet for some reason people feel they can shove giant patches at me without warning me and expect me to take it. I call this "code fisting." It's where you make a giant patch but don't write any tests, don't ask me if it's worth doing, and expect it to be applied now! Don't be a code-fister. I work on this stuff for fun, and really like helping people, but if you're going to give me a patch, be gentle. Tell me about it, communicate, send me the changes in small chunks, and make sure it's tested. I call this method of communicating change requests "code lube."

The worst thing you can do, though, is quote sections of the HTTP 1.1 RFC at me like you're a fire-and-brimstone minister yelling scripture out of the Bible at your flock. I don't think any Web server actually conforms to the HTTP 1.1 RFC because it's vague and complex. Many requirements in the RFC only apply in certain contexts and sometimes they contradict other sections. Rather than being a rules lawyer and throwing a paragraph of the RFC out of context at the bug tracker, go off and implement the requested feature yourself. Code is the currency of respect in the open-source world; write some if you want respect.

Mongrel. Serving, Deploying, and Extending Your Ruby Applications
Mongrel. Serving, Deploying, and Extending Your Ruby Applications
ISBN: 9812836357
Year: 2006
Pages: 48 © 2008-2017.
If you may any questions please contact us: