collection count increases after each scan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Exaile |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The count of the number of songs in the collection increases by 18 after every rescan, automatic or user-called. For example, it will start up and report the correct number, 3872. After one rescan, the output is
Library rescan called
Running is False
File count: 3872
Created db for thread Thread-9
{'Thread-9': <sqlite3.Connection object at 0x9ff1368>}
Committing 1500 scanned tracks...
Closed db for thread Thread-9
Committing 1500 scanned tracks...
Count is now: 3872
but in the Exaile window it now reports 3890. Another rescan:
Library rescan called
Running is False
File count: 3872
Created db for thread Thread-12
{'Thread-12': <sqlite3.Connection object at 0xa007368>}
Committing 1500 scanned tracks...
Committing 1500 scanned tracks...
Closed db for thread Thread-12
Count is now: 3872
the count is now 3908.
Changed in exaile: | |
milestone: | none → 0.3.0 |
Changed in exaile: | |
status: | Fix Committed → Fix Released |
could not get this bug to duplicate with v 0.2.11 under Hardy Beta.