[tahoe-lafs-trac-stream] [tahoe-lafs] #1418: "cannot convert float NaN to integer" in next_power_of_k, during upload via helper

[tahoe-lafs]

#1418: "cannot convert float NaN to integer" in next_power_of_k, during upload via
helper
-------------------------+-------------------------------------------------
     Reporter:  rycee    |      Owner:  rycee
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  undecided
    Component:  code     |    Version:  1.8.2
   Resolution:           |   Keywords:  helper upload heisenbug
Launchpad Bug:           |  floatingpoint debian pycryptopp
-------------------------+-------------------------------------------------

Comment (by rycee):

 Ok, I downloaded pycryptopp version 0.5.29 and did two builds with it.
 Once with `--disable-embedded-cryptopp` and once without. I then ran
 `python setup.py test` on both. For the build that used the embedded
 version of Crypto++ this finished without any errors. For the one using
 the dynamically linked Crypto++ (v 5.6.0) it ended in failure and I'll
 make an attachment containing the output of the failed run.

 Note, when I used `--disable-embedded-cryptopp` it was built against the
 Debian version of Crypto++ 5.6.0 since I don't know how to convince
 `setup.py` to look for headers and libraries in a non-standard directory.
 It still fails in the same way, though, if I use LD_LIBRARY_PATH to force
 it to load the upstream Crypto++ 5.6.0. Using the same technique to force
 it to use Crypto++ 5.6.1 results in an undefined symbol error.

 I'm not entirely sure how to use a custom pycryptopp in a Tahoe build so I
 didn't try to use my two pycryptopp builds in Tahoe but I suppose the
 pycryptopp test is telling enough. Also, when I run the Tahoe build now
 (once I uninstalled the Debian pycryptopp) it downloads and builds
 pycryptopp using the embedded Crypto++; and as previously seen those
 builds are doing just fine.

 Anyway, I think it's safe to say that the Crypto++ embedded in pycryptopp
 doesn't exhibit the problem I encountered.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1418#comment:48>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage