We've got more performance improvements with the latest Weave 0.5pre3 as well as usability improvements:
- Better memory/network usage by processing in chunks - Only start syncing when the user is inactive - Automatic passphrase/password verification and ability to change them - Improved error handling with server back-off and messages
This will likely be the last release before Weave 0.5, so please help test out these newest changes. This particular version doesn't have any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe the server.
As always, please ask questions or provide comments here, file bugs, or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll release Weave 0.5 in about a week. https://wiki.mozilla.org/Labs/Weave/ReportingBugs
Could you please note when the crypto API changes in the release notes so I know to rebuild the OpenSolaris WeaveCrypto.so module instead of just copying the previous build? Real badness this time (core dump on sign in), etc. made this easy to spot. I just don't want a subtle change to slip by giving us all a black eye.
> We've got more performance improvements with the latest Weave 0.5pre3
> as well as usability improvements:
> - Better memory/network usage by processing in chunks
> - Only start syncing when the user is inactive
> - Automatic passphrase/password verification and ability to change them
> - Improved error handling with server back-off and messages
> This will likely be the last release before Weave 0.5, so please help
> test out these newest changes. This particular version doesn't have
> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
> the server.
> As always, please ask questions or provide comments here, file bugs,
> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
> release Weave 0.5 in about a week.
> https://wiki.mozilla.org/Labs/Weave/ReportingBugs
> We've got more performance improvements with the latest Weave 0.5pre3
> as well as usability improvements:
> - Better memory/network usage by processing in chunks
> - Only start syncing when the user is inactive
> - Automatic passphrase/password verification and ability to change them
> - Improved error handling with server back-off and messages
> This will likely be the last release before Weave 0.5, so please help
> test out these newest changes. This particular version doesn't have
> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
> the server.
> As always, please ask questions or provide comments here, file bugs,
> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
> release Weave 0.5 in about a week.https://wiki.mozilla.org/Labs/Weave/ReportingBugs
latest-weave.xpi is a symlink to the other file. Both will work, but
we update the latest-weave.xpi link when we make a release, so it's
always the latest.
On Thu, Jul 23, 2009 at 6:28 AM, WildcatRay<wildcatter1...@gmail.com> wrote:
> This is purely out of curiosity. Why are the latest versions named
> latest-weave instead of in this case weave-0.5pre3?
> On Jul 23, 3:24 am, Edward Lee <edi...@mozilla.com> wrote:
>> We've got more performance improvements with the latest Weave 0.5pre3
>> as well as usability improvements:
>> - Better memory/network usage by processing in chunks
>> - Only start syncing when the user is inactive
>> - Automatic passphrase/password verification and ability to change them
>> - Improved error handling with server back-off and messages
>> This will likely be the last release before Weave 0.5, so please help
>> test out these newest changes. This particular version doesn't have
>> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
>> the server.
>> As always, please ask questions or provide comments here, file bugs,
>> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
>> release Weave 0.5 in about a week.https://wiki.mozilla.org/Labs/Weave/ReportingBugs
It was hectic yesterday, and my neurons must've been fried. For some
reason, I assumed that we could check from JS whether a particular .so
(not interface) supported a given method call. So we thought the
change was backwards-compatible, when it's actually not. doh.
On Thu, Jul 23, 2009 at 5:33 AM, Gary Gendel<gagen...@gmail.com> wrote:
> Ed,
> Looks great!
> Could you please note when the crypto API changes in the release notes
> so I know to rebuild the OpenSolaris WeaveCrypto.so module instead of
> just copying the previous build? Real badness this time (core dump on
> sign in), etc. made this easy to spot. I just don't want a subtle
> change to slip by giving us all a black eye.
> Regards,
> Gary
> On 7/23/09 3:24 AM, Edward Lee wrote:
>> We've got more performance improvements with the latest Weave 0.5pre3
>> as well as usability improvements:
>> - Better memory/network usage by processing in chunks
>> - Only start syncing when the user is inactive
>> - Automatic passphrase/password verification and ability to change them
>> - Improved error handling with server back-off and messages
>> This will likely be the last release before Weave 0.5, so please help
>> test out these newest changes. This particular version doesn't have
>> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
>> the server.
>> As always, please ask questions or provide comments here, file bugs,
>> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
>> release Weave 0.5 in about a week.
>> https://wiki.mozilla.org/Labs/Weave/ReportingBugs
I have Weave working well at the moment. (server and clients) I haven't fully tested it yet, but I sure looks good so far. Even LDAP authentication, which it claimed was incomplete, works great.
One of the other things I was warned about was having webdav enabled on apache. Do you know if this is going to remain an issue long? One of my next projects is going to be to get network calendaring working on Evolution. What sort of problems will I run into when I enable webcal to do so? Or will I need to run the calendars off of a different server?
On Thu, Jul 23, 2009 at 11:16 AM, Darryl Moore<dar...@moores.ca> wrote:
> I have Weave working well at the moment. (server and clients) I haven't
> fully tested it yet, but I sure looks good so far. Even LDAP
> authentication, which it claimed was incomplete, works great.
> One of the other things I was warned about was having webdav enabled on
> apache. Do you know if this is going to remain an issue long? One of my
> next projects is going to be to get network calendaring working on
> Evolution. What sort of problems will I run into when I enable webcal to
> do so? Or will I need to run the calendars off of a different server?
> This will likely be the last release before Weave 0.5, so please help > test out these newest changes. This particular version doesn't have > any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe > the server.
I noticed the server code now has a 0.5 branch .. is that in use yet, ie should I upgrade my server?
Nope. The server uses the 0.3 API exclusively at the moment. Though
I believe that the 0.5 server is backwards-compatible, so you should
be OK even if you upgrade.
On Thu, Jul 23, 2009 at 6:45 PM, Jason Frisvold<xenopha...@gmail.com> wrote:
> On Jul 23, 2009, at 3:24 AM, Edward Lee wrote:
>> This will likely be the last release before Weave 0.5, so please help
>> test out these newest changes. This particular version doesn't have
>> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
>> the server.
> I noticed the server code now has a 0.5 branch .. is that in use yet,
> ie should I upgrade my server?
> latest-weave.xpi is a symlink to the other file. Both will work, but
> we update the latest-weave.xpi link when we make a release, so it's
> always the latest.
> Dan
> On Thu, Jul 23, 2009 at 6:28 AM, WildcatRay<wildcatter1...@gmail.com> wrote:
> > This is purely out of curiosity. Why are the latest versions named
> > latest-weave instead of in this case weave-0.5pre3?
> > On Jul 23, 3:24 am, Edward Lee <edi...@mozilla.com> wrote:
> >> We've got more performance improvements with the latest Weave 0.5pre3
> >> as well as usability improvements:
> >> - Better memory/network usage by processing in chunks
> >> - Only start syncing when the user is inactive
> >> - Automatic passphrase/password verification and ability to change them
> >> - Improved error handling with server back-off and messages
> >> This will likely be the last release before Weave 0.5, so please help
> >> test out these newest changes. This particular version doesn't have
> >> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
> >> the server.
> >> As always, please ask questions or provide comments here, file bugs,
> >> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
> >> release Weave 0.5 in about a week.https://wiki.mozilla.org/Labs/Weave/ReportingBugs
> We've got more performance improvements with the latest Weave 0.5pre3
> as well as usability improvements:
> - Better memory/network usage by processing in chunks
> - Only start syncing when the user is inactive
> - Automatic passphrase/password verification and ability to change them
> - Improved error handling with server back-off and messages
> This will likely be the last release before Weave 0.5, so please help
> test out these newest changes. This particular version doesn't have
> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
> the server.
> As always, please ask questions or provide comments here, file bugs,
> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
> release Weave 0.5 in about a week.https://wiki.mozilla.org/Labs/Weave/ReportingBugs
I wanted to report that firefox is still freezing while syncing using
weave 0.5pre3, but for some reason google doesn't allow me to post
this report, so i put it here: http://codepad.org/zQ16CASr
> On Jul 23, 9:24 am, Edward Lee <edi...@mozilla.com> wrote:
>> We've got more performance improvements with the latest Weave 0.5pre3
>> as well as usability improvements:
>> - Better memory/network usage by processing in chunks
>> - Only start syncing when the user is inactive
>> - Automatic passphrase/password verification and ability to change them
>> - Improved error handling with server back-off and messages
>> This will likely be the last release before Weave 0.5, so please help
>> test out these newest changes. This particular version doesn't have
>> any record changes, so upgrading from 0.5pre2 to 0.5pre3 will not wipe
>> the server.
>> As always, please ask questions or provide comments here, file bugs,
>> or join us on irc.mozilla.org #labs. Hopefully if all goes well, we'll
>> release Weave 0.5 in about a week.https://wiki.mozilla.org/Labs/Weave/ReportingBugs
On Fri, Jul 24, 2009 at 9:08 AM, janisozaur<janisoz...@gmail.com> wrote: > I wanted to report that firefox is still freezing while syncing using > weave 0.5pre3, but for some reason google doesn't allow me to post > this report, so i put it here: http://codepad.org/zQ16CASr
Thanks for doing some initial analysis on your situation janisozaur. It's very strange that you would have 973 entries looking up the "query id: # = .." mapping for a particular id. Do you have a lot of "smart tag" folders? Folders that show you all bookmarks tagged with a particular tag?
I'm assuming you're also using some automatic bookmark management add-on? There are a lot of "foreign" GUIDs in your log such as: "Changing GUID frl74nhm-1 to fp5vvr88-6". They're not the default Firefox GUIDs and they aren't Xmarks GUIDs either. But it seems like something is creating a lot of bookmarks for you, and when Weave tries to sync. your 3181 bookmarks, it needs to do a lot of work to make sure there aren't any duplicates.
|
