ruby-dev (Japanese) list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: xtkoba+ruby@gmail.com
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:51021] [Ruby master Bug#17626] FileUtils.cp may cause utime_failed
Date: Sat, 13 Feb 2021 13:25:45 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-90368.20210213132544.50087@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-17626.20210213114806.50087@ruby-lang.org>

Issue #17626 has been updated by xtkoba (Tee KOBAYASHI).


I compiled the following code by `x86_64-w64-mingw32-gcc`:
```
/* -*- coding: utf-8 -*- */
#include <stdio.h>
void touch(char *path) {
  FILE *file = fopen(path, "a");
  if (file != NULL) fclose(file);
}
int main() {
  touch("fooコピー");
  return 0;
}
```
and when I ran the output executable on Windows 10, I got a file with a funny name:
```
$ echo -n foo* | hexdump -C
00000000  66 6f 6f c3 a3 e2 80 9a  c2 b3 c3 a3 c6 92 e2 80  |foo.............|
00000010  9d c3 a3 c6 92 c2 bc                              |.......|
00000017
```

When I ran the following Ruby script in the directory where the funny file exists, then I got no errors:
```
// -*- coding: utf-8 -*-
File.utime 0, 0, "fooコピー"
```

I cannot summarize this phenomenon, but I think it has something to do with the main issue.

----------------------------------------
Bug #17626: FileUtils.cp may cause utime_failed
https://bugs.ruby-lang.org/issues/17626#change-90368

* Author: agate-pris (agate pris)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x64-mingw32]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
FileUtils.cp will cause utime_failed if the file name contains Japanese characters and preserve is true.

This will probably only happen on Windows. It occures on Windows 10 version 2004 build 21301.1010.

``` ruby
require 'fileutils'

FileUtils.cp('foo', 'foo_copy', preserve: true)
FileUtils.cp('foo', 'fooコピー', preserve: true)
```

``` sh
$ ruby test.rb
C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:1424:in `utime': No such file or directory @ utime_failed - fooコピー (Errno::ENOENT)
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:1424:in `copy_metadata'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:515:in `copy_file'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:433:in `block in cp'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:1597:in `block in fu_each_src_dest'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:1613:in `fu_each_src_dest0'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:1595:in `fu_each_src_dest'
        from C:/tools/ruby30/lib/ruby/3.0.0/fileutils.rb:432:in `cp'
        from test.rb:4:in `<main>'
```

The expected result is copy to fooコピー is success same like copy to foo_copy.




-- 
https://bugs.ruby-lang.org/

  reply	other threads:[~2021-02-13 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 11:48 [ruby-dev:51020] " agate.pris
2021-02-13 13:25 ` xtkoba+ruby [this message]
2021-02-14  2:29 ` [ruby-dev:51022] " xtkoba+ruby
2021-02-14 12:07 ` [ruby-dev:51023] " agate.pris
2021-02-16  4:17 ` [ruby-dev:51024] " naruse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-90368.20210213132544.50087@ruby-lang.org \
    --to=xtkoba+ruby@gmail.com \
    --cc=ruby-dev@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).