General

Profile

hsbt (Hiroshi SHIBATA)

  • Login: hsbt
  • Email: hsbt@ruby-lang.org
  • Registered on: 04/26/2009
  • Last sign in: 04/30/2026

Issues

open closed Total
Assigned issues 34 405 439
Reported issues 14 223 237

Projects

Project Roles Registered on
Ruby Committer, Contributor, Release Manager, Security team, Infrastructure team 01/25/2013

Activity

Today

03:51 AM Ruby Bug #22065 (Closed): `make rdoc` fails with `invalid byte sequence in US-ASCII` on Ruby 4.0.4 under C locale
Building Ruby 4.0.4 in an environment where `Encoding.default_external` is `US-ASCII` (e.g. a Docker container with `LC_ALL=C`) fails while documenting `object.c`:
```
(ArgumentError) invalid byte sequence in US-ASCII
.bundle/gems/r...
hsbt (Hiroshi SHIBATA)

05/11/2026

09:04 AM Ruby Bug #22063: Regexp timeout accepts NaN and disables timeout
FYI: I deleted duplicated issues like #22061 and 22062 hsbt (Hiroshi SHIBATA)

05/09/2026

06:16 AM Ruby Revision c61a2f79 (git): [ruby/syntax_suggest] Make benchmark exapmles as optional
https://github.com/ruby/syntax_suggest/commit/ea73ed586a hsbt (Hiroshi SHIBATA)
06:16 AM Ruby Revision 963085bc (git): [ruby/syntax_suggest] Resolve to lint failure of standardrb
https://github.com/ruby/syntax_suggest/commit/ce7b87184e hsbt (Hiroshi SHIBATA)
06:16 AM Ruby Revision 5b17dd7a (git): [ruby/syntax_suggest] bundle exec standardrb --fix
https://github.com/ruby/syntax_suggest/commit/54bb8ab330 hsbt (Hiroshi SHIBATA)

05/08/2026

09:38 AM Ruby Bug #21995 (Assigned): mkmf generates a non-deterministic log file
I will look this. hsbt (Hiroshi SHIBATA)
09:31 AM Ruby Revision 0f618b87 (git): [ruby/rubygems] Allow non-zero exit status in bundle config gemfile unset spec
After 607648d5fc9 (`bundle config get` exits 1 when the value is unset),
the spec added in 4658d6bd78b raises in the bundle helper because the
new test invokes `config get gemfile` after unsetting it.
Co-Authored-By: Claude Opus 4.7 (1M...
hsbt (Hiroshi SHIBATA)
06:43 AM Ruby Revision 95ce1c52 (git): [ruby/rubygems] Honor LazySpec overrides in SpecSet#complete_platform
complete_platform validates platform-specific candidates returned by
spec.source.specs.search, which are remote specs that do not carry
the override list. Borrow the override list from the LazySpec exemplar
already in scope so platform-v...
hsbt (Hiroshi SHIBATA)
06:43 AM Ruby Revision 6a506224 (git): [ruby/rubygems] Avoid forcing a remote gemspec load when seeding LazySpec overrides
SpecSet#with_overrides cascaded into each contained spec via
`respond_to?(:overrides=)`. RemoteSpecification#respond_to? forwards
to _remote_specification, which materializes the backing gemspec just
to answer the predicate. spec/runtime...
hsbt (Hiroshi SHIBATA)
06:43 AM Ruby Revision 59706388 (git): [ruby/rubygems] Move overrides off SpecSet onto LazySpecification
SpecSet previously kept its own @overrides and a with_overrides setter
that had to be chained on every SpecSet.new(...) site (~13 sites in
Definition alone). Two Codex review rounds both flagged forgotten
chains in different SpecSet cons...
hsbt (Hiroshi SHIBATA)

Also available in: Atom