Ticket #136 (closed enhancement: released)

Opened 21 months ago

Last modified 20 months ago

Better explanation of lock failures

Reported by: richard Owned by: nobody
Priority: low Milestone:
Component: Backend-Flint Version: SVN trunk
Severity: minor Keywords:
Cc: Blocked By:
Operating System: All Blocking:

Description

The flint locking code can fail to obtain a lock in several different ways, but the user is not informed what the cause of the failure was. It would be nice if the user could be informed, by means of an informative message in the exception raised, why a lock couldn't be obtained.

Looking at the code, this would require the Lock object to return that information to the place that the exception is raised, or would require raising the exception to be moved into the Lock object.

Change History

Changed 21 months ago by olly

  • status changed from new to closed
  • resolution set to fixed

Fixed in SVN HEAD.

Changed 20 months ago by olly

  • resolution changed from fixed to released

Fixed in 1.0.0 release.

Changed 20 months ago by trac

  • platform set to All
Note: See TracTickets for help on using tickets.