-r date:today raises an unhandled exception when there have been no commit today.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
John A Meinel |
Bug Description
See traceback below.
I suppose the fix is just to catch the exception and provide a clean error message.
$ bzr log -r date:yesterday.
bzr: ERROR: bzrlib.
ator/') has no revision date:today
Traceback (most recent call last):
File "/home/
tch_errors
return run_bzr(argv)
File "/home/
ret = run(*run_argv)
File "/home/
liases
return self.run(
File "/home/
e
result = func(*args, **kwargs)
File "/home/
rev2 = revision[
File "/home/
tory
return self._match_
File "/home/
_on_and_check
raise NoSuchRevision(
NoSuchRevision: Branch BzrBranch5(
te:today
bzr 0.9.0dev0 on python 2.4.4.candidate.0 (linux2)
arguments: ['/home/
** please send this report to <email address hidden>
In general, when a revision spec tries to match, it should give a nice looking error if it cannot.
The problem is re-use of the 'NoSuchRevision' error. Which in some instances is a real bug, in others, (such as this) it was a simple invalid request. This is where we could set 'e.user_ error=True' , or just have a different exception for RevisionSpec.