Wednesday, December 19, 2012

Looking for work

Update: A colleague accepted a new job somewhere else. I am staying on but will have time for projects.

Der Freitag are laying off staff. The investor's financial situation has taken a turn for the worse, and the paper doesn't yet cover its costs (German link). My job is among the ones being cut.

Having something to do during the daytime makes life more bearable, so that's something i'd like to keep going. Fortunately, there is no shortage of developer jobs in Berlin.

Plone and related technologies are among my main areas of interest, but i'm keeping an open mind. As for the setting: working in a small company would be great, i'm also open to freelance offers. I enjoy working on Free Open Source Software, Web stuff, Python, and Linux, and i'm available from february.

If you know something that might be of interest to me, i'd much appreciate your feedback!

Kees

(khink on github, irc and plone.org, LinkedIn, firstnamelastname at gmail)

Monday, December 17, 2012

Shouldn't load state for ... when the connection is closed

Update: Suspicion has been falsified, as the same error occurred again yesterday.

We got this error from our live sites. Never locally, so hard to trace. One mailing list post warned that it might indicate a "severe persistency bug" which might cause "catastrophic inconsistencies". Most people agree that it's due to code that stores objects in inappropriate places (cached views).

That felt like looking for a needle in a haystack. We did find a viewlet that in its update method stored a portal tool on the viewlet, like so:

def update(self):
super(ViewletClass, self).update()
self.workflow_tool = getToolByName(self.context, 'portal_workflow') 

After replacing that line, the messages went away after the next update. Might be that something else that went into that update caused it, but i thought i'd share my suspicion here in case anyone ever googles for this.