There have been more instances of this problem, seemingly beyond Admin’s earlier explanation, with no input from Admin as of yet on these new instances, captured with screenshots. Please see UEN’s earlier post for the situation, plus the new updates.
EDIT: Admin’s many locks and responses are reposted in comments below.
EDIT (by starrydesigns): Read about the latest incident here.
EDIT: (by Soap) - latest update here - click.
July 23rd, 2007 at 5:35 pm
Sorry, mistyped in my last post.
wrong:
“2 different threads during V2″
should read:
“2 different threads BEFORE V2″
July 23rd, 2007 at 5:34 pm
I’m getting the ‘failure’ notices, too. *sigh*
Your points, JB, are probably right on the mark - and quite distressing.
And façade, wasn’t there also a much more recent incident of chat confusion?
I wish I could understand the hesitation of admin to not only acknowledge this problem, but to simply get cracking on a solution. It is in their best interests to keep things running as smoothly and securely as possible. What possible motive could there be for (initially) denying, then dramatically downplaying this bug? What benefit is it to them to let the issue continue and escalate? Sorry - I just can’t wrap my mind around it at all.
Don’t they realize that members will respect them much more for an honest and prompt response - even if it’s to say “we goofed but we’re getting to the bottom of it ASAP”? I guarantee that they are losing not only respect, but also credibility with their current attitude.
July 23rd, 2007 at 5:29 pm
Deja Vu said,
July 23, 2007 @ 5:14 pm
“Green Mamba, I joined a bit prior, in February 2006. As I recall, there were not as many technical issues with the Beta version. There were stability problems, but no security issues that I am aware of…”
———-
I went skimming through the archives earlier. There were at least 2 different threads during V2 about logging into the wrong account. One of them referenced people posting in chat under the wrong username.
Again, I have no clue what changed in V2. This might not be the same problem at all. That’s why I’ve never brought it up on the forum.
I deeply resent Etsy’s accusations of panic-mongering.
July 23rd, 2007 at 5:17 pm
retroattic I am getting that same error for about the last 10 minutes.
refreshing has not resolved the problem for me.
I think all the locking of topics and labeling completely rational threads with loaded words like “panic” and “sensationalism” is trying to discredit all the victims and other posters as unreliable witnesses. It basically has a chilling effect so that other victims of the bug will be afraid to report it and perhaps also get labeled or blacklisted as troublemakers.
I also think that when they wait days to reply to these threads, they are hoping that the longer they wait, someone will get frustrated and will say something rude or a fight will break out . Then they will have justification to lock the topic.
Everyone, do not allow yourself to be manipulated. Keep your posts on etsy as stoic as the sphinx, focused, respectful. If a cheerleader tries to bait you with something dumb like “if you hate etsy so much why don’t you leave?”, don’t take the bait. People have every justification for being frustrated and alarmed, but when they express that, etsy has an easy “out” and can just dismiss us as hysterical troublemakers.
July 23rd, 2007 at 5:14 pm
I can’t get into the Etsy forum either, so much for it having its own database. *rolls eyes*
Green Mamba, I joined a bit prior, in February 2006. As I recall, there were not as many technical issues with the Beta version. There were stability problems, but no security issues that I am aware of, and technical issues were dealt with pretty well. There were bandaid solutions to some problems that have since actually been fixed well. But overall I don’t see V2 as much of an improvement, sadly. As well, the non-technical issues that concerned me (resellers, non-handmade goods, etc.) haven’t improved much. It seems to me that Admin have become less responsive to people’s concerns, probably because the user base has grown so much.
But these are just my opinions. I’d like to hear other people’s thoughts on how Beta compares to V2 as well.
July 23rd, 2007 at 4:58 pm
A question for you seasoned Etsians: I joined late in 2006, just prior to the V2 switch. Were there as many issues with the Beta version as there have been with this one? How were concerns dealt with? Were the admins more, or less, receptive to user concerns and input?
Okay, three questions. But I’m curious.
July 23rd, 2007 at 4:53 pm
Well, alex, I suppose that is always an option. Unfortunate. I hope that is not what it will take to get the admins to not only take this - and the users - seriously, but to stop patronizing us with false or misleading info.
July 23rd, 2007 at 4:50 pm
I am unable to read teh new thread because I keep getting this stupid error which was supposedly fixed yesterday according to RD. I’m SICK of the lies!!!!!
FAILURE: Exception occured Traceback (most recent call last): File “/home/svnuser/Projects/Etsy/trunk/emid/emid/MethodCaller.py”, line 86, in __call__ data = method(*args) File “/home/svnuser/Projects/Etsy/trunk/emid/emid/SQLInterface.py”, line 155, in wrapped results = SQLInterfaceFunc(tmpl, a, Pool) File “/home/svnuser/Projects/Etsy/trunk/emid/emid/logutil.py”, line 109, in new_func res = func(*a, **b) File “/home/svnuser/Projects/Etsy/trunk/emid/emid/SQLInterface.py”, line 325, in getOneRecord desc, results = procSQL_return_one_record(sql, args, Pool) File “/home/svnuser/Projects/Etsy/trunk/emid/emid/Resources.py”, line 156, in procSQL_return_one_record conn = Pool.getconn() File “/home/svnuser/Projects/Etsy/trunk/emid/emid/thirdparty/pool.py”, line 149, in getconn return self._getconn(key) File “/home/svnuser/Projects/Etsy/trunk/emid/emid/thirdparty/pool.py”, line 88, in _getconn raise PoolError(”connection pool exausted”) PoolError: connection pool exausted >
You are on webserver
Time July 23, 2007, 8:46 pm
This should be a momentary issue — please try refreshing this page in a few minutes!
July 23rd, 2007 at 4:49 pm
will = with
ooops
And I, too, find it quite odd that admin are not soliciting more details about these logons. You’d think the more info they have, the better they’d be able to track down and isolate the cause(s). Whenever there are viewing issues, or treasury problems, etc. RD and jared always ask for specifics. But not here.
July 23rd, 2007 at 4:46 pm
If this is a continuing problem then one quite effective - and very professional - place to complain is the Better Business Bureau - http://www.bbb.org/complaint.asp
If several people file complaints, with evidence, it is pretty much bound to be taken seriously.
The trouble is that even a suggestion like this seems to be taken by Etsy admin as a threat. It isn’t intended to be, it’s just a good fall-back to know about if there seems to be no other way of getting the problem resolved.