ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: deivid via ruby-core <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: deivid <noreply@ruby-lang.org>
Subject: [ruby-core:119820] [Ruby master Bug#20704] Windows: `-C` option does not work for multibyte path name
Date: Thu, 07 Nov 2024 19:06:09 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-110508.20241107190608.4@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20704.20240828121437.4@ruby-lang.org>

Issue #20704 has been updated by deivid (David Rodríguez).


Hello @nobu!

One bundler spec started failing after upgrading our CI to use Ruby 3.3.6 on Windows. The error reads like this:

```
  Invoking `C:/hostedtoolcache/windows/Ruby/3.3.6/x64/bin/ruby.exe -ID:/a/rubygems/rubygems/bundler/spec -rD:/a/rubygems/rubygems/bundler/spec/support/artifice/fail.rb -rD:/a/rubygems/rubygems/bundler/spec/support/hax.rb D:/a/rubygems/rubygems/bundler/tmp/1.4/gems/system/bin/bundle config path D:/a/rubygems/rubygems/bundler/tmp/1.4/♥/vendor/bundle` failed with output:

  ----------------------------------------------------------------------
  Error: Command line contains characters that are not supported
  in the active code page (1252).
  ----------------------------------------------------------------------
# ./spec/support/command_execution.rb:26:in `raise_error!'
# ./spec/support/subprocess.rb:66:in `sh'
# ./spec/support/helpers.rb:213:in `sys_exec'
# ./spec/support/helpers.rb:107:in `bundle'
# ./spec/commands/install_spec.rb:1262:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:105:in `block (4 levels) in <top (required)>'
# ./spec/spec_helper.rb:105:in `block (3 levels) in <top (required)>'
# ./spec/support/helpers.rb:342:in `block in with_gem_path_as'
# ./spec/support/helpers.rb:356:in `without_env_side_effects'
# ./spec/support/helpers.rb:337:in `with_gem_path_as'
# ./spec/spec_helper.rb:104:in `block (2 levels) in <top (required)>'
```

The spec passed just fine on Ruby 3.3.5.

I wonder if this change is related.

Thank you!

----------------------------------------
Bug #20704: Windows: `-C` option does not work for multibyte path name
https://bugs.ruby-lang.org/issues/20704#change-110508

* Author: nobu (Nobuyoshi Nakada)
* Status: Closed
* Backport: 3.1: REQUIRED, 3.2: DONE, 3.3: DONE
----------------------------------------
Related to [Bug #20699].


```
C:> \Ruby33-x64\bin\ruby.exe -C xテスト_test -ep
\Ruby33-x64\bin\ruby.exe: Can't chdir to xテスト_test (fatal)
```

https://github.com/ruby/ruby/pull/11493



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

  parent reply	other threads:[~2024-11-07 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 12:14 [ruby-core:118976] " nobu (Nobuyoshi Nakada) via ruby-core
2024-10-21  8:50 ` [ruby-core:119541] " nagachika (Tomoyuki Chikanaga) via ruby-core
2024-11-04 22:36 ` [ruby-core:119708] " k0kubun (Takashi Kokubun) via ruby-core
2024-11-07 19:06 ` deivid via ruby-core [this message]
2024-11-08 17:55 ` [ruby-core:119849] " deivid via ruby-core

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-110508.20241107190608.4@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@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).