#136 closed enhancement (released)
Better explanation of lock failures
| Reported by: | Richard Boulton | Owned by: | Not currently assigned |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Backend-Flint | Version: | SVN trunk |
| Severity: | minor | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Operating System: | All |
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 (2)
comment:1 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
| Operating System: | → All |
|---|---|
| Resolution: | fixed → released |
Fixed in 1.0.0 release.
Note:
See TracTickets
for help on using tickets.
Fixed in SVN HEAD.