Exception "bzr: ERROR: Could not acquire lock" occurs very often.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Explorer |
Fix Released
|
High
|
Jonathan Riddell |
Bug Description
By newest release(1.2.0),
I see exception dialog very very often, which says "bzr: ERROR: Could not acquire lock".
It occurs after executing commit, push, pull, and other many commands.
Turning off 'Automatically refresh status report' does not solve it.
(BTW, I doubt that this preference does not work,
because bzr-explorer still puts "QFileSystemWat
TRACEBACK(In .bzr.log)
-------
60.548 Traceback (most recent call last):
File "***\explorer\
self.
File "***\explorer\
lines = self.report_text()
File "***\explorer\
model.relpath)
File "***\explorer\
self.
File "***\explorer\
pending_merges = status_
File "***\explorer\
status.
File "***\\lib\
parents = new.get_
File "***\\lib\
self.
File "***\\lib\
state.
File "***\\lib\
self.
File "***\\lib\
win32file.
File "***\\lib\
raise errors.
LockContention: Could not acquire lock "***/m4_
VERSION
--------
Bazaar (bzr) 2.4b5
Python interpreter: C:\DEVELOP\
Python standard library: C:\DEVELOP\
Platform: Windows-7-6.1.7600
bzrlib: C:\DEVELOP\
Bazaar configuration: C:\Users\
Bazaar log file: C:\Users\
Related branches
- Jelmer Vernooij (community): Needs Information
- Bazaar Explorer Developers: Pending requested
-
Diff: 109 lines (+31/-15)2 files modifiedlib/view_workingtree.py (+20/-11)
lib/wt_browser.py (+11/-4)
Changed in bzr-explorer: | |
status: | Confirmed → Fix Released |
Changed in bzr-explorer: | |
milestone: | none → 1.2.1 |
assignee: | nobody → Jonathan Riddell (jr) |
I think, background status refreshing should ignore lock error (and retry after a interval), or notify it by something like a baloon, not a modal dialog.