[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2235: Error from 'tahoe cp' on Windows, due to a long path (IOError: Errno2 - no such file or dir.)

[Tahoe-LAFS]

#2235: Error from 'tahoe cp' on Windows, due to a long path (IOError: Errno2 - no
such file or dir.)
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  Zancas
  CyberAxe               |     Status:  new
         Type:  defect   |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  code-    |   Keywords:  tahoe-cp error windows win32 test-
  frontend-cli           |  needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by daira):

 Replying to [comment:15 zooko]:
 > The next step on this should be to write a test, perhaps in
 [source:trunk/src/allmydata/test/test_util.py], that attempts to create a
 file under a long filename in the (real, not faked) local filesystem, and
 if the file is successfully created then the test passes. That test should
 be red on current trunk when run on Windows, and go green when
 [https://github.com/daira/tahoe-
 lafs/commit/2a2a1adee5f814fa8018fe4119e4daf843dc229a daira's patch] or
 another fixit-patch is applied.

 I agree that we need such a test.

 > I don't understand this `not path.startswith(u"\\\\")` clause in Daira's
 patch, and I'd like to see a second test added to the one described above,
 which verifies that whatever behavior is intended by that clause is what
 actually happens.

 This has been done.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2235#comment:23>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage