Bug 15940 – BMF non-recursive rescan is broken

Bug 15940 - BMF non-recursive rescan is broken

Summary:

BMF non-recursive rescan is broken

Status:	RESOLVED WORKSFORME

Product:	SB Touch
Classification:	Unclassified
Component:	TinySC
Version:	unspecified
Platform:	Other Other

Importance:	P1 major (vote)
Target Milestone:	Investigating
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-03-23 09:01 UTC by Andy Grundman
Modified:	2013-08-16 05:08 UTC (History)
CC List:	6 users (show)

See Also:
Category:	Bug

Attachments
log file when this happened (52.59 KB, text/plain) 2010-03-26 04:08 UTC, Michael Herger	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Andy Grundman 2010-03-23 09:01:20 UTC

In non-recusive mode the new scanner is broken, and thinks you have deleted all 
your files except the ones in the single directory.

Comment 1 Chris Owens 2010-03-25 09:14:23 UTC

Michael says he copied a bunch of new files to his music folder and just browsed in.

Comment 2 Michael Herger 2010-03-25 09:20:06 UTC

More details: 
- embedded branch running on PC using CentOS 4 based OS, with perl 5.10
- copied a folder from my Mac using Samba -> old folder got replaced (deleting existing tracks)
- on the server I copied old files from the backup -> folder then had old and new files/folders in it
- used Boom to BMF
-> all displays of all attached devices got stuck on whatever they were displaying (clock stuck for several minutes)
-> Boom never entered the MF

-> SBS had completely wiped the DB

Comment 3 Michael Herger 2010-03-26 04:08:18 UTC

Created attachment 6708 [details]
log file when this happened

The log would go on and on with the remaining 15k tracks. This is only the first few dozens.

Comment 4 Chris Owens 2010-03-29 10:58:30 UTC

I tried this several times this morning and couldn't easily reproduce it.  I totally believe that it did happen, but it doesn't seem like it should block 7.5.0

Comment 5 Chris Owens 2010-04-12 16:25:27 UTC

Still can't reproduce this