"remote server did not return a token" assertion error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Benjamin Heitmann <email address hidden> reports:
Hello, as requested by the error dump, I forward the error message to
this mailing list.
I was trying to commit for the first time to a repository using the
dirstate-tags format.
I am using bzr on a mac. Had it compiled form source via fink, but
had to update to 0.92 because of the new branch format.
Here is the whole error message.
-------
chapultepec:
$ bzr commit -m "finished the survey part. its up to page 6 now, with
slimmed black and white pictures"
Password:
bzr: ERROR: exceptions.
token!
Traceback (most recent call last):
File "/sw/lib/
802, in run_bzr_
return run_bzr(argv)
File "/sw/lib/
758, in run_bzr
ret = run(*run_argv)
File "/sw/lib/
492, in run_argv_aliases
return self.run(
File "/sw/lib/
2315, in run
author=author)
File "/sw/lib/
165, in write_locked
return unbound(self, *args, **kwargs)
File "/sw/lib/
line 244, in commit
result = WorkingTree3.
**kwargs)
File "/sw/lib/
165, in write_locked
return unbound(self, *args, **kwargs)
File "/sw/lib/
187, in commit
revprops=
File "/sw/lib/
in commit
self.
File "/sw/lib/
in _check_bound_branch
self.
File "/sw/lib/
token=
File "/sw/lib/
assert self._lock_token, 'Remote server did not return a token!'
AssertionError: Remote server did not return a token!
bzr 0.92.0 on python 2.5.1.final.0 (darwin)
arguments: ['/sw/bin/bzr', 'commit', '-m', 'finished the survey part.
its up to page 6 now, with slimmed black and white pictures']
encoding: 'US-ASCII', fsenc: 'utf-8', lang: None
plugins:
launchpad /sw/lib/
plugins/launchpad [unknown]
multiparent /sw/lib/
plugins/
** Please send this report to <email address hidden>
with a description of what you were doing when the
error occurred.
Changed in bzr: | |
importance: | Undecided → Medium |
I have the feeling this was a newer bzr client trying to talk to an older bzr server, and the server didn't know about returning tokens for lock requests.
I don't think you'll encounter this if you upgrade both client and server to newer versions of bzr. (As this is bzr 0.92, there have been a lot of improvements since then.)