linuxdcpp-team team mailing list archive

[eMTee <919424@xxxxxxxxxxxxxxxxxx>]

If anyone still cares I suggest splitting this conversation and moving
comments #12 and #13 to a new feature wishlist entry as the original
report here is about the hashdata.dat cleaning process does not start in
some cases - which is still an issue at the moment with DC++ 0.867.

IIRC the error itself happens because of an incomplete refactoring of threading code a few versions before the time when the original report has been filed. The /rebuild process does not start (blocked) if a manual or automatic share refresh process has already started before. 
I am surprised that this conclusion has not been added to this thread yet - maybe a separate duplicate entry of this issue exists?

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/919424

Title:
  /rebuild does not update HashData

Status in ApexDC++:
  New
Status in DC++:
  Confirmed

Bug description:
  BCDC 0.790a. 
  Windows 7 SP1 x64.

  Summary:
  If you add a new share, hash the files, and then remove it, issue a /rebuild and then re-add the same share again, DC++ will not rehash the files. Furthermore, a /rebuild between adding/removing shares does not change the size of hashdata.dat or hasindex.xml.

  Repro:
  * add a new share. accept the default name. DC++ hashes the files.
  * open your filelist to validate share is present.
  * check the size of hashdata and hashindex.
  * remove the share you just added.
  * issue a /refresh and /rebuild.
  * note the size of hashdata and hashindex has NOT changed.
  * add the same share again, accepting the default name.  DC++ does NOT hash the files.
  * issue a /refresh. DC++ does not re-index the files from that share.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apexdc/+bug/919424/+subscriptions