Folks,
Revision 3295 of sync-engine SVN now contains a number of cleanups to
the error handling in the tools - this was largely in response to a
number of reports from users being confused by exception tracebacks. Now
if a tool is run without sync-engine running, or is run incorrectly, or
no devices are present, a much more informative message is displayed.
During testing of this release, another bug has surfaced which is now
known about. If you disconnect the device at certain points during the
actual run of an Airsync device sync loop, there is a likelihood that
sync-engine will lock up. I'll fix this shortly.
John.
Excerpt from the changelog:
---------------------------
Fixed typo in _CheckDeviceConnected leading to confusing exceptions
being generated when tools are run without a device connected.
Considerably improved error handling in the tools. Errors such as
sync-engine not running, devices not connected and the like are handled
cleanly and generate informative error messages. Added usage string to
create_partnerships. This should prevent tracebacks being displayed to
the user unless there really is an error, as opposed to bad input or
configuration.
This will hopefully reduce the number of bug reports caused by issues
such as sync-engine not running, or a device not connected correctly.
Updates to errors.py augment the error handling structure.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
