Last modified: 2009-07-14 06:16:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20970, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18970 - Fatal error prevents small number of people from voting
Fatal error prevents small number of people from voting
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
SecurePoll (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-28 01:27 UTC by Robert Rohde
Modified: 2009-07-14 06:16 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Robert Rohde 2009-05-28 01:27:00 UTC
Three people, enwiki users RichardRothwell, Apeiron, and Oaktree_b, reported a permanent fatal error that prevented them from voting.  They each appear qualified to vote and appeared to be following the process correctly.

In each case when they arrived at SPI they recieved an "Internal Error" message along with the "Set $wgShowExceptionDetails = true;" boilerplate.  This was a persistent condition occurring every time these accounts attempted to vote.

Their report suggest to me that the associated account data at SPI was erroneously or incompletely generated.  Possibly the database got overloaded when they first visited and something was dropped?

Whatever the cause these editors were totally blocked from voting.  Since this was reported only 3 times with >18000 ballots cast, it is obvious that whatever caused this condition is an unusual and hard to replicate problem.
Comment 1 Tim Starling 2009-07-14 05:47:28 UTC
There's no way I can isolate this without any exception message or backtrace. I'll keep an eye out for potential exceptions but I can't promise anything.
Comment 2 Robert Rohde 2009-07-14 06:16:51 UTC
Then you should probably at least change configurations to allow the backtrace to be displayed.  As it is they are given an error message with no usable details.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links