Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • http://www3.pic-upload.de/20.11.09/2p2cb6hi298.png [pic-upload.de]

    The forms are placed so that it looks ugly and they have no labeling.

    I made a test comment and previewed. That error message sucks. Then I went over to Dave's blog to write this report and was not able to comment there, either.

    Where on MAGnet can I chat with y'all to exchange more information?

    • You can shoot an email to Dave Cross's gmail account (davorg). A couple of other errors have cropped up, too. Believe it or not, this is far better than when it started :)

    • What browser and version are you using? The site looks much nicer to me.

  • If I try and register, I either get an internal server error or Text entered was wrong. Try again.
  • We're aware of the 500 errors that many people are getting when signing in (or out). Seems to be some kind of resource issue.

    I'm looking into it. Sorry for the inconvenience.

  • I'm sorry, but how does one work for a year on a website but not get the login working right?

    I was a bit interested in it, unlike all the previous "goodbye, cruel use Perl;" attempts, but clicking the button on the signup page I got a "can't fork page" error, then trying to login after a few tries it now says "This account has been disabled. Please see your system administrator for access.". Incredible! Maybe it's just me, but I find this to be a major turnoff...

    • We weren't working on it for a year. There have been a number of attempts on the project and this, most recent, version has been built in a couple of months.

      We're still investigating the problem, but it seems that our error was in capacity planning. During two weeks of testing we have seen very few errors, but once the entire Perl community started looking at the site, the server couldn't cope.

      Yes, it's disappointing. But I can assure you that no-one is as disappointed as me today.

      I can only apologise again

    • As Dave pointed out, the site itself is actually very new. The idea has been around for a long time, but there were some false starts which were looked at and discarded. As mentioned, the site is alpha. It worked fine, but it turned out that when plenty of people hit it, there were memory issues. Given that it's a a fresh launch of a new site built by volunteer labor who freely admit that it's alpha code, it's understandable that there will be bugs. Regrettably, the nature of bugs is that they're unkno

  • FWIW, I hit some fairly evil bugs too, but looking again after a few hours, they seem to have gone away without any real effort on my part.

    So yay for attentive admins, and thank you greatly guys for your hard work.