Is it just me, or do others also often find that rt.cpan.org is very slow and/or down ?
I've just spent over 30 minutes trying to submit a bug report. Eventually, after numerous exceedingly slow downloads and Internal Server Errors, I was able to get to the page where I get to write the bug report (the writing of which took me no more than 5 minutes).
Then I click on the "Create" button, wait for a couple of minutes, walk away in impatient disgust, come back to see yet another Internal Server Error, go "Back", and find that the report I had so carefully written is no longer there. Great ... that means I have to write it again ...
This is by no means the first time that I have been frustrated in trying to submit a bug report. Do they want my bug report or not ?
Anyway, I guess the lesson is: "Write your bug reports to a (saved) text file, so that when rt.cpan.org stuffs you around, re-submitting the bug report is as simple as doing a copy'n'paste.
Cheers,
Rob
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.