[Cherokee-dev] Issue 1356 in cherokee: Cherokee website community forum is down

[cher...@googlecode.com]

Status: New
Owner: ----

New issue 1356 by carsten....@gmail.com: Cherokee website community forum
is down
http://code.google.com/p/cherokee/issues/detail?id=1356

What steps will reproduce the problem?
1. Visit http://www.cherokee-project.com/community.html
2. Get a 500 error

What is the expected output? What do you see instead?
A working community page

What version of the product are you using? On what operating system?
Irrelevant



_______________________________________________
Cherokee-dev mailing list
Cherok...@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

[cher...@googlecode.com]

Comment #1 on issue 1356 by j.vonpreussen: Cherokee website community forum
is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Error 500: INTERNAL SERVER ERROR

Traceback (most recent call last):
File "/space/src/www.cherokee-ctk/CTK/Server.py", line 185, in
handle_request
content = self._do_handle()
File "/space/src/www.cherokee-ctk/CTK/Server.py", line 140, in _do_handle
ret = published (**published._kwargs)
File "/space/src/www.cherokee-ctk/PageCommunity.py", line 50, in __call__
page.sidebar += ProudList.DomainList()
File "/space/src/www.cherokee-ctk/ProudList.py", line 86, in DomainList
latest_widget = DomainList_Widget()
File "/space/src/www.cherokee-ctk/ProudList.py", line 62, in __init__
domains = cPickle.load (open (config.PROUD_PICKLE, 'r'))
EOFError

[cher...@googlecode.com]

Updates:
Status: Accepted
Owner: alobbs
Labels: Type-Defect Priority-Critical Component-Web

Comment #2 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

We would need access to that part of the website to fix that. Problem
acknowledged. Sorry it takes so long.

[cher...@googlecode.com]

Comment #3 on issue 1356 by jeremy.m...@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

There is a pickle file specified in config.py

https://github.com/cherokee/web/blob/d7730d9863ad1ea3a0736510dae2f6c150199c05/config.py

which is corrupt on the server. IMO the code needs to embed a reasonable
(empty?) default so that the main community board is robust against
failures to load this particular list of proud domains running Cherokee
from a pickle. I have submitted a github pull request with an
implementation of this exception handler.

[cher...@googlecode.com]

Comment #4 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Issue 1363 has been merged into this issue.

[cher...@googlecode.com]

Comment #5 on issue 1356 by carsten....@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Come on guys - how hard can it be? That's a shame.

[cher...@googlecode.com]

Comment #6 on issue 1356 by jeremy.m...@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

How hard: need to release the fix. Not sure who has access to the webserver
to perform that work.

[cher...@googlecode.com]

Comment #7 on issue 1356 by carsten....@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

A community forum down for months? That's usually a sign of really bad
leadership or a decaying project.

[cher...@googlecode.com]

Comment #8 on issue 1356 by j.vonpreussen: Cherokee website community forum
is down
http://code.google.com/p/cherokee/issues/detail?id=1356

i realize that mr. lobb's erstwhile "labor of love" now suffers from his
lack of time/attention due to a new job and that -- apparently -- some
volunteers have been trying to fill the breach. however, the "community"
deserves a place to hash out problems and seek work-arounds to the many
deficiencies now not being adequately addressed in a timely manner.

if this self-aggrandizement file cannot be corrected or eliminated, perhaps
we need to start a new forum with a simple DNS change. losing access to
whatever archives exist on the current defective system seems virtually
cost-free given that no service at all is certainly a major negative cost.

[cher...@googlecode.com]

Comment #9 on issue 1356 by psaod8fz...@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

This was no forum. Discussion is Happening on the Mailing lists. I don't
think there is a big lost of wisdom here.

Also: Same as http://code.google.com/p/cherokee/issues/detail?id=501 ;)

[cher...@googlecode.com]

Comment #10 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Issue 1389 has been merged into this issue.

[cher...@googlecode.com]

Comment #11 on issue 1356 by j.vonpreussen: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

the attn this issue has NOT garnered over the past 3/4 year is indicative
of what i, personally, have come to regard as a "dead horse".

i have moved on to openresty (a bundled nginx implementation). the memory
foot-print is far, far smaller; execution far faster; and attentive
world-wide interest/support almost surfeit in comparison to cherokee. the
only thing missing is the config gui and that has had its own problems
right along.

too bad!

[cher...@googlecode.com]

Comment #12 on issue 1356 by daniel.n...@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Stefan, could you please remove the community link from the cherokee web
site? I think as long as it's not working, it should be removed to not
confuse people and generate useless bug reports like #1393.

[cher...@googlecode.com]

Comment #13 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

I am not able to alter the Cherokee website. So it should become a top
priority to change the website to github-pages...

[cher...@googlecode.com]

Comment #14 on issue 1356 by daniel.n...@gmail.com: Cherokee website

community forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Is Alvaro able to do it? If it takes two months to migrate the web page,
it's two more months with a broken page, that may be partially fixed right
now by removing the link ;)

[cher...@googlecode.com]

Updates:
Owner: ste...@konink.de

Comment #15 on issue 1356 by alobbs: Cherokee website community forum is
down
http://code.google.com/p/cherokee/issues/detail?id=1356

I do believe the website should be migrated to Github. I'll change the DNS
entry as soon as the new one is ready.

Thanks for following up on this folks!

[cher...@googlecode.com]

Comment #16 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Issue 1381 has been merged into this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[cher...@googlecode.com]

Comment #17 on issue 1356 by ste...@konink.de: Cherokee website community

forum is down
http://code.google.com/p/cherokee/issues/detail?id=1356

Issue 1373 has been merged into this issue.