Two of the nasties are mine, and I've been using a month-old build of
Chandler until recently, when I upgraded it on one of the machines that
I use but not the other. I wonder if it's the combination of using an
ancient (as Morgen described it :-) client in combination with a more
up-to-date one that's caused at least some of issues that I've run into.
Would you suggest keeping up with the most recent build at least every
few days? Starting with a clean repo or keeping the old one if the
schema hasn't changed?
Davor
On Thu, 9 Aug 2007, Philippe Bossut wrote:
Hi,
We just had our (now daily) Bug Council and we still have 11 bugs open so, no
ZBR for today again...
The real concern though is about a list of 6 nasty repo bugs that are piling
and hard to repro, track and, more than likely, fix. Here's the list:
9920 AttributeError: 'pem' while syncing with
https://hub.chandlerproject.org
10349 Cannot select-all in Dashboard
10384 "Unknown EIM translation problem" error when syncing
10391 "NoSuchAttributeError" for "CalendarSelection.selectedOccurrences"
during syncing
10401 Traceback when starting chandler
10402 Adhoc and other index errors
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
